# Problems with run node red start

**URL:** <https://discourse.nodered.org/t/problems-with-run-node-red-start/82610>\
**Category:** General\
**Created:** [4 November 2023 20:47 UTC](https://discourse.nodered.org/t/problems-with-run-node-red-start/82610 "2023-11-04T20:47:03Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jacol184](https://avatars.discourse-cdn.com/v4/letter/j/e19b73/32.png) [@jacol184](https://discourse.nodered.org/u/jacol184)\
**Post date:** [4 November 2023 20:47 UTC](https://discourse.nodered.org/t/problems-with-run-node-red-start/82610/1 "2023-11-04T20:47:03Z")

</div>

Suddenly my node red stopped working, reinstalling does not solve the problem :  
logs

i Node-RED works better with the Firefox or Chrome browser

Use node-red-stop to stop Node-RED  
Use node-red-start to start Node-RED again  
Use node-red-log to view the recent log output  
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot  
Use sudo systemctl disable nodered.service to disable autostart on boot

To find more nodes and example flows - go to [http://flows.nodered.org](http://flows.nodered.org)

Starting as a systemd service.  
4 Nov 19:46:01 - [error] [tensorflowCoco:0e076ed9ba64afbc] Error: /home/jacol/.node-red/node\_modules/@tensorflow/tfjs-node/lib/napi-v8/tfjs\_binding.node: wrong ELF class: ELFCLASS64  
4 Nov 19:46:01 - [info] Started flows  
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] login -\> \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*wXOVV  
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] SEND -\> Cmd: LOGIN, Id: 1, len: 32, data: "\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*wXOVV"  
4 Nov 19:46:02 - [info] [blynk-ws-client:Hormann\_CH1234] login -\> \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*sdUIW  
4 Nov 19:46:02 - [info] [blynk-ws-client:Hormann\_CH1234] SEND -\> Cmd: LOGIN, Id: 1, len: 32, data: "\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*sdUIW"  
(node:8445) Warning: Setting the NODE\_TLS\_REJECT\_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.  
(Use `node --trace-warnings ...` to show where the warning was created)  
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] RECV \<- Cmd: RSP, Id: 1, responseCode: OK  
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] Client logged  
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] SEND -\> Cmd: INTERNAL, Id: 2, len: 85, data: "ver|0.6.1|h-beat|15|buff-in|32767|dev|node-red|con|Blynk-ws|fw|1.0.9|build|2023-01-12"  
4 Nov 19:46:02 - [info] [blynk-ws-client:40e46c9aaa2b12b0] Client logged  
4 Nov 19:46:02 - [info] [blynk-ws-client:Weather] Client logged  
4 Nov 19:46:02 - [info] [blynk-ws-client:Pir\_status] Client logged  
4 Nov 19:46:02 - [info] [blynk-ws-client:Hormann\_CH1234] RECV \<- Cmd: RSP, Id: 1, responseCode: OK  
4 Nov 19:46:02 - [info] [blynk-ws-client:Hormann\_CH1234] Client logged  
4 Nov 19:46:02 - [info] [blynk-ws-client:Hormann\_CH1234] SEND -\> Cmd: INTERNAL, Id: 2, len: 85, data: "ver|0.6.1|h-beat|15|buff-in|32767|dev|node-red|con|Blynk-ws|fw|1.0.9|build|2023-01-12"  
4 Nov 19:46:02 - [info] [blynk-ws-client:2953ef1774a8a3b1] Client logged  
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] virtualWrite: -\> ["vw","35","NaN"]  
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] SEND -\> Cmd: HW, Id: 3, len: 9, data: "vw|35|NaN"  
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] RECV \<- Cmd: RSP, Id: 2, responseCode: OK  
4 Nov 19:46:02 - [info] [blynk-ws-client:Hormann\_CH1234] RECV \<- Cmd: RSP, Id: 2, responseCode: OK  
4 Nov 19:46:02 - [red] Uncaught Exception:  
4 Nov 19:46:02 - [error] SyntaxError: Unexpected token I in JSON at position 0  
at JSON.parse ()  
at Request.\_callback (/home/jacol/.node-red/node\_modules/node-red-contrib-blynk-api/blynk-api.js:448:27)  
at Request.self.callback (/home/jacol/.node-red/node\_modules/request/request.js:185:22)  
at Request.emit (node:events:513:28)  
at Request. (/home/jacol/.node-red/node\_modules/request/request.js:1154:10)  
at Request.emit (node:events:513:28)  
at IncomingMessage. (/home/jacol/.node-red/node\_modules/request/request.js:1076:12)  
at Object.onceWrapper (node:events:627:28)  
at IncomingMessage.emit (node:events:525:35)  
at endReadableNT (node:internal/streams/readable:1358:12)  
at processTicksAndRejections (node:internal/process/task\_queues:83:21)  
nodered.service: Main process exited, code=exited, status=1/FAILURE  
nodered.service: Failed with result 'exit-code'.  
nodered.service: Consumed 13.185s CPU time.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [4 November 2023 21:28 UTC](https://discourse.nodered.org/t/problems-with-run-node-red-start/82610/2 "2023-11-04T21:28:34Z")

</div>

> [@jacol184](#):
>
> 4 Nov 19:46:02 - [red] Uncaught Exception:  
> 4 Nov 19:46:02 - [error] SyntaxError: Unexpected token I in JSON at position 0  
> at JSON.parse ()  
> at Request.\_callback (/home/jacol/.node-red/node\_modules/node-red-contrib-blynk-api/blynk-api.js:448:27)

You have a node causing an "Uncaught Exception"

That node is `node-red-contrib-blynk-api`

To get up and running, uninstall that node using`npm remove node-red-contrib-blynk-api` from `/home/jacol/.node-red`

Also, report the error to the author by raising an issue on the GitHub repository.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [4 November 2023 21:36 UTC](https://discourse.nodered.org/t/problems-with-run-node-red-start/82610/3 "2023-11-04T21:36:33Z")

</div>

You might want to walk away from `node-red-contrib-blynk-api` - and try your luck with a different Node.

 ![Screenshot 2023-11-04 at 21.35.48](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/1/61e2d255744e177c7a6cb10665409e4aaa36bdfc.png)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [4 November 2023 21:42 UTC](https://discourse.nodered.org/t/problems-with-run-node-red-start/82610/4 "2023-11-04T21:42:30Z")

</div>

If you stop node-red then restart using  
`node-red --safe`  
it will start up in safe mode, with the editor enabled but no flows running. That should stop the node from crashing node-red and you can try to fix the flow that is causing the problem. When you deploy it will start the flows.

---

<div class="post-metadata">

**Author:** ![jacol184](https://avatars.discourse-cdn.com/v4/letter/j/e19b73/32.png) [@jacol184](https://discourse.nodered.org/u/jacol184)\
**Post date:** [5 November 2023 08:53 UTC](https://discourse.nodered.org/t/problems-with-run-node-red-start/82610/5 "2023-11-05T08:53:24Z")

</div>

Thank you guys, it worked. 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [19 November 2023 08:54 UTC](https://discourse.nodered.org/t/problems-with-run-node-red-start/82610/6 "2023-11-19T08:54:16Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.