Frequent Editor Disconnects with Multi-Instance?

I am running 2 instances of Node-RED (different paths different ports etc under systemd) on a raspberry pi. It's all working fine, but I am noticing that the web editor for the development/test instance is frequently disconnecting from the server. (It may be that this is happening with my production instance also but I am not in the editor for it so frequently, so I may not be noticing it.)

Any thoughts/recommendations please? (My next step will probably be to move my development instance to a separate machine.)

What do you mean by disconnecting?

If you run node-red-log at the same time what do you see there?

Are you running the browser showing the editor on the Pi? Do you see the same problem if you run the browser on a PC?

Please stop and restart node red and post the startup log. Copy/paste please, not screenshot.

I am getting a banner at the top of the screen saying: "Lost connection to server, reconnecting..."

I am running the editor on a Mac browser.

I've found the culprit: I did systemctl restart nodered.service && journalctl -fu nodered.service and after a while saw an uncaught exception on a configuration node that I was no longer using. Removing it allows all to start and stay up.

Thanks for pointing me in the right direction - it's pretty obvious in hindsight that I should have checked that the process was actually running.

I suspected that it might be occasional restarts.

1 Like

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