Web socket client config crashes node-red when local server is down


When the local server is not available the websockets node config causes a continuous stream of error close messages which after 3-4 minutes swamps the buffer and crashes node-red. I am on latest server version and I updated the nodes to the latest as well. The only way to stop it crashing the node-red system is to delete the access config node although it is difficult as the node red becomes very unresponsive and often crashes again before you can delete the node and redeploy.

The nodes should surely respond more gracefully if the server is offline. This happens constantly even where there is access ongoing

Hi Steve,

Did you find the route cause of this. I’m encountering the same problems and I guess Im on a much more recent server than when you had these issues.

Exactly the same… can’t make it stable

1 Like