Lost connection to server, reconnecting

General
21

I have been trying to figure out why this "Lost connection to server, reconnecting" keeps showing up (for the past year at least). It doesn't matter which version of node-red I'm using, and it happens on Safari on Mac and Safari on iPhone.

I also cannot see any "debug" messages (and none in the log). So no console.out are getting displayed, but debug module outputs go to the node-red.log file.

Someone mentioned there is a WebSocket between node-red and the browser. This might explain why no debug messages since the "connection to the server" is lost.

My apps use lots of Websockets and MQTT as well (in case this interferes?).

NOTE: I use port 2000 (not 1880) is this an issue? (After a bitcoin hack)

And I'm using an AWS linux (debian?) install. Things work fine on my macs.

Also: [warn] rpi-gpio : Raspberry Pi specific node set inactive

I have the latest of everything. Any ideas?
thanks
scott

22

I'm facing similar problem, i have a node-red running behind the firewall, so I opened 1880 port for specific domain. But I can see always this error "Lost connection to server, reconnecting in xxs. Try now..." on the dashboard and debug is not showing any log information. I also can see what the were attempts to connect to ws://mydomain/comms with the Gateway error 502. Any suggestion how I can resolve it?

23

I was having the same issue "Lost connection to server, reconnecting..." in my node-red that lives inside a Docker container with nginx as a reverse proxy. In my case the issue was that my nginx config did not upgrade the WebSockets request properly. I had to add this lines in my nginx config for my site after the "location /":

proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";

Maybe there is a similar configuration in other servers.

24

Yes, each proxy server has something similar.

Though I have noticed just recently that my NGINX proxy does not seem to be letting Socket.IO upgrade from HTTPS to WSS and I'm not sure why yet, not had time to do any investigation. I'm sure it was working fine.

Not at home at the moment so can't do any work on it.