When I recently disabled SSL on my hassio, my log was also filled with these errors. The difference is that I was still able to access the frontend. For me, the fix was to change "ssl": true to "ssl": false in the configurations of the addons that had that field.
Being that you don’t have frontend access, maybe you can change the addon configurations via SSH? I’m not sure, though, so someone else will have to chime in on that.
Thank you guys. Removing the base url did the magic.
I can access the Webinterface again and Node Red can connect to it.
Greetings
I’m trying to get this to work as well, but with Caddy instead of Nginx, I have “a.duckdns.org” pointing to my hassio frontend and “b.duckdns.org” pointing to NodeRED, I am able to access both services through those urls, but when I use “a.duckdns.org” as the server base url in NodeRED I get the
Cannot GET /homeassistant/entities
I’ve tried using localhost:8123 as the base url with no luck. Any ideas?
Apparently it doesn’t connect until the flow is deployed, all is well now.
my conifguration.yaml has only
http:
but when I click on START in the NGINX addon, nothing happens (I forwarded port 443 to 443 of the IP of the NUC that has HASSIO)
You’d have to look at the logs to see what’s going wrong. BTW, that should no longer be necessary to do now that hassio supervisor 0.78 has been released. You can just configure Node-RED to use http://hassio/homeassistant as the Base URL now regardless of whether you have SSL enabled or not.
How you configure this?
{
“ssl”: false,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,
“users”: [
{
“username”: “admin”,
“password”: “password”,
“permissions”: “*”
}
],
“http_node_user”: [
{
“username”: “admin”,
“password”: “password”
}
]
}
Ok, I installed all.
Now what do I have to change my configuration and leave only the below code?
http:
base_url: http://hassio/homeassistantIt’s not referring to base_url in Home Assistant configuration. If you install node-red-contrib-home-assistant in Node-RED, then you can use http://hassio/homeassistant as the Base URL for that node.
it will take me another 3-4 yars before I understand all that buzz
Here is a great blog post that may help.
my doubts are more on http https letsencrypt, nginx, caddy, port 8123 443, forward router base_url, ssl, tls … I find it extremely confusing
Oh, I thought you were asking about Node-RED since that’s what this topic is about. Since that’s not related to the Node-RED addon, you might be better off creating a new topic.
can you make the addon work for Intel?
It already works on 64-bit Intel processors…
Hey quick question regarding this configuration, under domain name in ngix
do you use this as your config?
domain : “https://xxxxduckdns.org”
Just your domain name by itself.
{
"domain": "xxxx.duckdns.org",
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
}
I would like to through this out concerning connections from inside and outside you router. I have hassio and node red installed on a pi3. I also set up duckdns which allows me to access hassio from outside my home. I opened port 8123 (pin hole) on my router for hassio with dusckdns. node red was not accessible until i also opened port 1880. Ok so I started working with nod red and set up the server in node red as https://myaddress.duckdns.org:8123 (address of my hassio). Set up some basic node red flows and all works great. Was looking around for some help so I imported some node red flows from the web. Import works great but the server that was set up for the imported flows was http://localhost:8123 (forgot to mention I have a password set up for my hassio). Once deployed, open the debug window and get a continuous error that node red can’t connect to the server on http://localhost:8123 because the password was rejected. Deleting the imported flow doesn’t stop the loop. The only way I found to stop the loop was to delete all of the server definitions and re-deploy my original duckdns server on each node in all of the flows. Deleting the one bad flow or even redefining the server in each node of the imported flow doesn’t work.
You have to delete to bad server and re-set the imported flows to your correct server before deploy or you get the continuous loop.
I noticed the same exact behavior after importing some flows yesterday. Thanks for posting the workaround, this is really helpful. I got so frustrated yesterday that I nuked my entire node-red install and started over again from scratch.