Problem/Motivation

Hello, so I am having a very frustrating issue. Node-red is installed properly via the hass.io add-on. I configured the software as follows:

So I started troubleshooting where I thought best, I checked to make sure the docker container was running. It is running and the logs have no errors. Here is the pastebin link for the node-red logs: https://pastebin.com/54RwPGLh

So next I wanted to make sure that Node-RED was actually running, even though it says it is in the logs. So I open port 1880 on my server, and head over to 192.168.1.x:1880 and it lets me in. The UI is loaded fine.

So next I started reading around and found a few articles. The first was about an old local storage cache, well that is not my issue because this is a brand new install, and I have never used node-red on this computer. Just for the sake of it, I double checked and I was correct no storage items, so that was a dead end.

Next I was thinking and decided maybe the HA/supervisor logs had something for me, and sure enough in the supervisor logs I found the following line occured every time I navigated to node-red from the hassio interface: 19-07-02 15:51:19 ERROR (MainThread) [hassio.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:62819 ssl:None [Host is unreachable]

Here is a copy of the supervisor log in pastebin: https://pastebin.com/jredy7zJ A few errors I see, not sure if these are related or even matter:

19-07-02 15:01:33 ERROR (MainThread) [hassio.utils.gdbus] DBus return error: b'Error: Timeout was reached\n'
19-07-02 15:01:33 WARNING (MainThread) [hassio.dbus.hostname] Can't connect to hostname

19-07-02 15:01:33 ERROR (MainThread) [hassio.utils.gdbus] DBus return error: b'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name de.pengutronix.rauc was not provided by any .service files\n'
19-07-02 15:01:33 WARNING (MainThread) [hassio.dbus.rauc] Can't connect to rauc

Here is a copy of the home assistant log in pastebin: https://pastebin.com/6ub6Ui76

Well okay, maybe something got screwy during the docker setup. Lets check the routes and make sure the interfaces are configured properly:

[root@TCH-HA homeassistant]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    100    0        0 ens192
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
172.30.32.0     0.0.0.0         255.255.254.0   U     0      0        0 hassio
192.168.1.0     0.0.0.0         255.255.255.0   U     100    0        0 ens192

Yup, routes are fine that cant be the issue either.. Then it struck me, I am working behind a reverse proxy that proxies the traffic over to the HA box. So let's eliminate that and just connect locally. Maybe that is the issue! I head over to http://192.168.1.x:8123/a0d7b954_nodered and unfortunately the same thing. I saw on another forum that some people get it to work using the Open Web UI button, but no luck here still a 502 error.

I am at the end of the straw and can't seem to find another possible solution. Any help would be appreciated.

Expected behavior

Obviously we expect that the node-red interface will appear in either the sidebar or open web ui link.

Actual behavior

502: Bad Gateway on Open Web UI or the side bar, but can connect to the node-red UI without using HA by going to 192.168.1.x:1880