I am attempting to try out HA mode. I have created a development Instance and a production instance. When I turn my Production Instance on to HA mode my instance will not run. My dashboard will just say “X Connection Lost”. Am I doing something wrong or is there a problem with the way my instance is setup? How do I fix this?
Do you mean the Node-RED editor or a Dashboard UI instance?
When enabling HA mode the Node-RED editor is disabled because when 2 instances are running, connecting the editor would lead to changes only being made to a single instance of the backend. To solve this you should make use of DevOps pipelines to promote changes from the development instance to the production instances.
Also when enabling HA mode the existing instance will be restarted (to pick up the changes to the settings) so I would expect the Dashboard UI to be disconnected while 2 instances start up.
By “Dashboard” I mean a Dashboard UI. Yes I am using the dev-ops to push my flows into the HA instance. That part works fine. However the HA instance does not do anything after I load it. The Dashboard UI is still down after 30 min. It usually only takes 30-60 seconds after the flow says it has started. Something is not working right. What do I try next?
Robert VanHofwegen
District Manager
Paloma Irrigation and Drainage District
You can’t access a Node-RED instance running in HA via a web interface (either the editor or any Dashboards you deploy). This is because there is no way to determine which of the HA copies of Node-RED is responding to an attempt to access the dashboard. If you could access the dashboard your interactions with it would be unpredictable at best and totally inoperable a lot of the time.
If you want to deploy a dashboard driven by a HA application I’d suggest you run a separate instance of Node-RED specifically for the dashboard. You can use our project in and project out nodes to pass data between your HA and non-HA instances.
Just to be clear here, this is down to how the node-red-dashboard is implemented, something we hope to fix in the new version that is currently under development. It doesn’t support multiple instances, because it’s using the Socker-IO library.