# ERROR in node-red run

**URL:** <https://discourse.nodered.org/t/error-in-node-red-run/10799>\
**Category:** General\
**Created:** [4 May 2019 06:00 UTC](https://discourse.nodered.org/t/error-in-node-red-run/10799 "2019-05-04T06:00:18Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![chirag](https://avatars.discourse-cdn.com/v4/letter/c/ecccb3/32.png) [@chirag](https://discourse.nodered.org/u/chirag)\
**Post date:** [4 May 2019 06:00 UTC](https://discourse.nodered.org/t/error-in-node-red-run/10799/1 "2019-05-04T06:00:18Z")

</div>

AFTER USING MODBUS SERVER NODE MY NODE-RED IS NOT WORKING.

 ![node-red%20error](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/4/4112342804966d5d017d624fec9adda8dbf50ace.png)

PL GUIDE TO SOLVE.

---

<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 May 2019 07:46 UTC](https://discourse.nodered.org/t/error-in-node-red-run/10799/2 "2019-05-04T07:46:47Z")

</div>

You should post this screen shot on the GitHub repo as an issue. The node is not correctly handling socket issues.

To get back in to node-red, add command line parameter `--safe` when you launch it.

E.g. `node-red --safe`

This will start node red without starting flows. That will allow you to edit and remove the node which is crashing node-red.

---

<div class="post-metadata">

**Author:** ![chirag](https://avatars.discourse-cdn.com/v4/letter/c/ecccb3/32.png) [@chirag](https://discourse.nodered.org/u/chirag)\
**Post date:** [4 May 2019 07:49 UTC](https://discourse.nodered.org/t/error-in-node-red-run/10799/3 "2019-05-04T07:49:15Z")

</div>

thank you for your reply.  
its helpful.

---

<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 May 2019 09:32 UTC](https://discourse.nodered.org/t/error-in-node-red-run/10799/4 "2019-05-04T09:32:24Z")

</div>

As @Steve-Mcl says there is a bug in the node as it should catch that problem and not crash node-red. As to why it is happening, do you have a choice over the port number you are using ( 502)? Regular users cannot normally listen to port numbers below 1024 which may be the root of the problem. If you can change it to a higher number then perhaps you can avoid the problem.

---

<div class="post-metadata">

**Author:** ![chirag](https://avatars.discourse-cdn.com/v4/letter/c/ecccb3/32.png) [@chirag](https://discourse.nodered.org/u/chirag)\
**Post date:** [4 May 2019 09:41 UTC](https://discourse.nodered.org/t/error-in-node-red-run/10799/5 "2019-05-04T09:41:17Z")

</div>

yes its worked.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [4 May 2019 10:02 UTC](https://discourse.nodered.org/t/error-in-node-red-run/10799/6 "2019-05-04T10:02:44Z")

</div>

Please can you also open an issue on the nodes github page as @Steve-Mcl suggested.

A node should not cause Node-RED to crash and it is something the author should fix.

You can follow a link to the nodes github page by following the link from the nodes page on [flows.nodered.org](http://flows.nodered.org)

---

<div class="post-metadata">

**Author:** ![chirag](https://avatars.discourse-cdn.com/v4/letter/c/ecccb3/32.png) [@chirag](https://discourse.nodered.org/u/chirag)\
**Post date:** [4 May 2019 10:17 UTC](https://discourse.nodered.org/t/error-in-node-red-run/10799/7 "2019-05-04T10:17:25Z")

</div>

ok  
i will open an issue on github.