Ingress support has been added, which means the add-on works via the cloud connection as well, simply by clicking the “OPEN WEB UI” button on the add-on page.
You can still enable the “old” direct access method, by setting a port in the network section of the add-on configuration panel.
Hey Frenck, On the direct access method on port 1880, the HA credentials are failing upon login. keeps asking for credentials.
Updated and everything seems to work. However, there is no info anymore showing when I node was last triggered and the Debug node does not show any information in the Debug panel.
Update, got Debug and Statuses to work by accessing hassio directly (ip:port) instead thru reverse proxy - so seems to be an issue when going thru reverse proxy server.
Same issue here.
Same here as well… at least using chrome. Using the WebGui link opens the “embeded” version but still does not login, showing an empty page with just the nodered logo on top.
Shift+F5 end up showing:
Update: Using Firefox the external site is working including login
In case it wasn’t clear for hass.io, to add a button in the sidebar, add something like this to configuration.yaml:
panel_custom:
- name: hassio-main
sidebar_title: Node-RED
sidebar_icon: mdi:wrench
js_url: /api/hassio/app/entrypoint.js
url_path: nodered
embed_iframe: true
require_admin: true
config:
ingress: a0d7b954_nodered
The ingress value may differ; when you click on the add-on in Hass.io, look at the end of the URL and use that.
While I am using the ingress for the web UI, I use direct access for a web socket connection from my smart meter box. I have a POST node:
[
{
"id": "f75b678a.15f718",
"method": "post",
"name": "",
"swaggerDoc": "",
"type": "http in",
"upload": false,
"url": "/eagleenergy",
"wires": [
[
"14341499.f6b37b",
"685b7d4e.bbd174",
"a50a796.8193688"
]
],
"x": 130,
"y": 100,
"z": "7765c2a1.8ef4ac"
}
]
Which listens on /eagleentery on port 1880. Is there a way to disable authentication or use some type of token that I can append to the URL that I add to my smart meter?
Thanks!
Replying to my own post, adding leave_front_door_open to the config and removing the username/password is letting my POST get through. I wish there was a way to secure the web UI, but allow other access. Maybe in a future version.
STATUS: The port method doesn’t let me login. On the Ingress method, I’m seeing webpage loading errors. This happens when accessing it the second time on the http load not on the https(works fine on https)…
Clearing cache helps load once again on http(local ip) and when i try to load page the second time it fails again to load and then i see the below page errors.
Https (port 1880) login is possible for me but only using firefox, chome is not working. (ssl enabled via addon config/ ssl is not enabled for HA itself). The Ingress method is not working for me at all.
Looking to get a different adress to use with panel_iframe. When I take the url when using the web_ui from the add_on page and try to use it with panel_iframe I get the panel doubled. I had the same problem with configurator but was able to find another url following the instructions from this page:
When I look at the adress I have for node_red it is:
https://redacted.duckdns.org:8123/hassio/ingress/a0d7b954_nodered
The adress I got for the configurator is:
https://redacted.duckdns.org:8123/api/hassio_ingress/partiallyredactedp_bozBtcSU_QOroLZMqE6ZjcE/
It is interesting to se the different structure
hassio/ingress/…
vs.
api/hassio_ingress/…
Anyone who knows how to find the corresponding adress for node red?
I’ve been having a lot of trouble accessing Node-RED after 3.0. To access via ingress I seem to have to force refresh every single time in order to get it to load at all. Otherwise it just loads the basic frame but no content. When it does load, many of the icons for nodes are broken images. Which ones seem to vary. In addition, sometimes I have to force reload several times to get it to load. This is in Chrome.
After first enabling the port method again, I had the issue where it asked for credentials over and over and never loaded. But after clearing all my browser data, port method seems to be working and reliably loading.
Hi,
Any way to enable access via up address and port number again?
Regards
WD
Accessing node red via the 1880 port seems to work in chrome incognito mode.
Might be a cache issue when the login pops up all the time?
Any advice on how to troubleshoot please. NodeRed has been running fine but when i tried to upgrade yesterday to 3.0 using the Hassio webinterface i get the following error message.
I tried uninstalling NodeRed in the addons and rebooting, and then trying to install from scratch but same issue.
Running
Plenty of disk space.
After upgrade to 3.0.0 and setting network port running in to issues accessing Node Red instance via reverse proxy. Monitoring tools like uptimerobot and freshping do not see Node Red as up while it’s running just fine if accessing directly. Also log now shows all web activity which didn’t show before?
I wish I could have a choice to use Ingress or not. This is a major breaking change.
This is an unfortunate docker issue that points to some corruption in the filesystem. It’s been coming up a lot lately but I think the common factor is a pi and SD ? I may be wrong.
The best thing to do is reflash and restore from snapshot, since the fix involves removing everything anyway.
Thanks. Reflashed the sd card from the RPI, Grabbed last nights snapshot, Wipe and Restore and it now allows me to upgrade.
For people who opened direct access by enabling and setting the port to 1880 and experiencing repeated login cycles. This might be a solution to resolve it:
It seems like node-red stored a piece of information about the login system used in versions of the node-red add-on before v3.0.0 (e.g., v2.0.2).
This authentication method does not exist anymore but nevertheless, throws off Node-RED so it seems.
Removing this manually helps in all the tests I’ve done tonight.
Hi,
I found the underlying adress. I found it under (in this case Safari) developer/web inspector/network/documents
The adress is in the format:
https://redacted.duckdns.org:8123/api/hassio_ingress/“longstring”
I pasted this as my node red url for panel iframe and it worked as before. No need to enable any ports.
I reached it immediately from my iMac. I initially had problems with my iPad (unauthorized 401). But if I first entered either add-on (I also have configurator) from the web ui link on the I could access it directly from the panel.
