# Node-red editor does not load

**URL:** <https://discourse.nodered.org/t/node-red-editor-does-not-load/10516>\
**Category:** General\
**Created:** [24 April 2019 18:59 UTC](https://discourse.nodered.org/t/node-red-editor-does-not-load/10516 "2019-04-24T18:59:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![manueldiasmanuel](https://avatars.discourse-cdn.com/v4/letter/m/3d9bf3/32.png) [@manueldiasmanuel](https://discourse.nodered.org/u/manueldiasmanuel)\
**Post date:** [24 April 2019 18:59 UTC](https://discourse.nodered.org/t/node-red-editor-does-not-load/10516/1 "2019-04-24T18:59:28Z")

</div>

Hi,

... after deploying Node-Red it has stopped running and i´ve got a " red level " code as you can see below. How to recover from this situation ?

24 Apr 19:53:17 - [info] Node-RED version: v0.20.5  
24 Apr 19:53:17 - [info] Node.js version: v10.15.3  
24 Apr 19:53:17 - [info] Linux 4.14.98-v7+ arm LE  
24 Apr 19:53:18 - [info] Loading palette nodes  
^A24 Apr 19:53:22 - [info] Dashboard version 2.13.2 started at /ui  
24 Apr 19:53:23 - [info] Settings file : /home/pi/.node-red/settings.js  
24 Apr 19:53:23 - [info] Context store : 'default' [module=memory]  
24 Apr 19:53:23 - [info] User directory : /home/pi/.node-red  
24 Apr 19:53:23 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/)  
24 Apr 19:53:23 - [info] Active project : HomeAmorim  
24 Apr 19:53:23 - [info] Flows file : /home/pi/.node-red/projects/HomeAmorim/flows\_localhost.json  
24 Apr 19:53:23 - [info] Starting flows  
24 Apr 19:53:23 - [info] [mosca in:2f73359.33167ca] Binding mosca mqtt server on port: 1883  
2019-04-24 18:53:24: Connecting to modbustcp slave at 192.168.1.23:502 unit\_id: 1  
2019-04-24 18:53:24: Connecting to modbustcp slave at 192.168.1.22:502 unit\_id: 1  
24 Apr 19:53:24 - [info] Started flows  
24 Apr 19:53:24 - [info] [mqtt-broker:80a21c84.84208] Connection failed to broker: mqtt://127.0.0.1:1883  
_24 Apr 19:53:24 - [red] Uncaught Exception:_  
24 Apr 19:53:24 - RangeError [ERR\_OUT\_OF\_RANGE]: The value of "value" is out of range. It must be \>= 0 and \<= 4294967295. Received 1556132004270  
at checkInt (internal/buffer.js:35:11)  
at writeU\_Int32BE (internal/buffer.js:619:3)  
nodered.service: Main process exited, code=exited, status=1/FAILURE  
nodered.service: Unit entered failed state.  
nodered.service: Failed with result 'exit-code'.  
nodered.service: Service hold-off time over, scheduling restart.  
Stopped Node-RED graphical event wiring tool.  
Started Node-RED graphical event wiring tool.

Regards

MD

---

<div class="post-metadata">

**Author:** ![manueldiasmanuel](https://avatars.discourse-cdn.com/v4/letter/m/3d9bf3/32.png) [@manueldiasmanuel](https://discourse.nodered.org/u/manueldiasmanuel)\
**Post date:** [24 April 2019 19:26 UTC](https://discourse.nodered.org/t/node-red-editor-does-not-load/10516/2 "2019-04-24T19:26:40Z")

</div>

I found the solution for my problem.

Thanks.

Regards,

MD

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [24 April 2019 19:33 UTC](https://discourse.nodered.org/t/node-red-editor-does-not-load/10516/3 "2019-04-24T19:33:55Z")

</div>

> [@manueldiasmanuel](#):
>
> found the solution for my problem.

For the benefit of anyone else reading this, what was the solution?

---

<div class="post-metadata">

**Author:** ![manueldiasmanuel](https://avatars.discourse-cdn.com/v4/letter/m/3d9bf3/32.png) [@manueldiasmanuel](https://discourse.nodered.org/u/manueldiasmanuel)\
**Post date:** [24 April 2019 20:31 UTC](https://discourse.nodered.org/t/node-red-editor-does-not-load/10516/4 "2019-04-24T20:31:44Z")

</div>

Agree.

First, i knew that the error was related with a wrong value i have manually injected to simulate a function. So i decided to open/edit flow file \> flows\_localhost.json ... and i could disabled the tab where the problematic node was. I could than restart Node-Red without issues.  
Final step, i edit the node that was creating the problem. I reenabled the tab and deployed. Node-Red was running well again.

PS: It´s a honor to chat with you. I ´m a very very basic node-red user ...and contributing for this amazing tool that is Node-Red ... uauu 😀

Regards,

MD