node-red-dashboard icon indicating copy to clipboard operation
node-red-dashboard copied to clipboard

Connection Lost on node-red-dashboard

Open isehuetdk opened this issue 4 years ago • 0 comments

What are the steps to reproduce?

Hosting Node-RED on a Kubernetes behind NGINX Ingress Controller. Connecting to the Editor works fine, when opening the UI it is being presented correctly but after a few seconds I get a "Connection Lost" message. This message reappears every 20seconds or so. Test has been done from Chrome, IE and Microsoft Edge towards https://myClusterName/nodered/ui/. The connection happens towards the Load Balancer -> NGINX Ingress Controller -> Node-RED Ingress for Path prefix -> Node-RED Service -> Node-Red Pod. Same manifest has been deployed to Azure Kubernetes Service where the issue doesn't exist.

What happens?

In IE I get the error: SCRIPT12030: WebSocket Error: Network Error 12030, The connection with the server was terminated abnormally In Microsoft Edge and Chrome I see in the Developer Console the error "Failed to load resource: the server responded with a status of 404 ()". Everytime the "Connection Lost" appears, I can see a new socket.io call is made by index.js, (e.g. towards ?EIO=3&transport=polling&t=NYhYKTM), always with a new value t (topic/thread?). Seems like the websocket is being terminated.

No errors in the Node-RED Logs (also in Debug mode).

What do you expect to happen?

I don't expect the websocket session to be terminated. And no Connection Lost error to appear.

Please tell us about your environment:

  • [ ] Node-RED-Dashboard version: 2.28.2
  • [ ] Node-RED version: 1.2.9
  • [ ] node.js version: 10.23.0
  • [ ] npm version:
  • [ ] Platform/OS: Windows 10 20H2, Windows Server 2019 1809
  • [ ] Browser: Microsoft Edge 89.0.774.68, IE Windows Version 20H2, IE 1809, Chrome 89.0.4389.90

isehuetdk avatar Apr 07 '21 11:04 isehuetdk