Node-Red Dashboard does not open anymore after update

Third party integrations Node-RED
1

Hi

After applying the latest Updates I can’t access Node-red Dashboard anymore on the usual URL:

https://<local-IP>:8123/endpoint/ui

I also tried several other URL found in the forum:

https://<local-IP>:1880/endpoint/ui

https://<myhost.duckdns.org:8123/endpoint/ui
https://<myhost.duckdns.org:1880/endpoint/ui

https://hassio.local:8123/endpoint/ui
https://hassio.local:1880/endpoint/ui

I also added the following options to configuration.yaml, as indicated in the latest release notes:

   use_x_forwarded_for: true
   trusted_proxies: 127.0.0.1

I guess it was not specifically related to the very last updates, but rather showed now up after having the core restarted after the latest updates.

Node-red itself works fine.

HA WebGUI also still works fine.

Any help appreciated.

BR
Marc

2

You could look at the logs:
supervisor > nodered > protocol

or look for anything nodered related:
supervisor > system
or
configuration > logs

3

Node-red log shows that node-red dashboard has properly started:

3 Aug 11:38:33 - [info] Dashboard version 2.23.4 started at /endpoint/ui
-
3 Aug 11:38:34 - [info] Server now running at http://127.0.0.1:46836/

But supervisor can’t connect to nodered:

21-08-03 11:38:34 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:63784 ssl:default [Connect call failed ('172.30.32.1', 63784)]

Seems like the supervisor does not connect to the right IP:Port? Or is Nodered Dashboard not starting on right IP:Port?

4

Just to be sure. Did you restart the host (not just HA)?
You can do that from supervisor > system > restart host

5

Yes.

If I try without SSL (i.e. http:// ) I get a least a response, saying that http is relayed to https.

Meanwhile I did a complete re-installation of HA, and moved all configs and flows from the old to the new instance. Lost 4h, but at least everything works now.

Funny enough, the dashboard still does not work with https, only with http. Also HA Lovelace works fine with https…

6

Looks like you know more about it than me. I’m just using a reverse proxy, so I don’t care about SSL of my different services.

7

There has been something up with nodered and ssl/auth since may. System updates seem to bring up odd behavior. The most common being loss of debugging. Another is ssl access, I lost it after core update 7.4.

Some have had luck with complete reinstalls, some like yourself, it does nothing. I’m just leaving it as ssl off, using http since it’s only local for me.

8

I will try the “NGINX Home Assistant SSL proxy” Add on. Using reverse proxy for SSL handling with components like node-red seems to be the cleaner approach to handle SSL across services / applications on HA anyway.

9

Thank you for that information. Glad to know that it is not something only showing on my installation. For now http works fine, but as I have all automations implemented in node-red, I would feel a bit better having the node-red dashboard protected by SSL.