I was having the same issue - the solutions above seemed fine if I wanted to expose nodered to the internet (eg. port forwarding etc) but I just wanted nodered to be accessible locally (while HA was open to the internet with letsencrypt & duckdns setup).
I tried all the same URL’s as the original posted - turned out the solution was to just add an entry to my hosts file on the pi so calls from nodered were just looped back to the local interface when yourdomain.duckdns.org:8123 was called.
Hi Wayne, two of the solutions mentioned above don’t require any port forwarding and don’t expose Node Red to the internet.
Thanks for posting your solution though! The more solutions that are mentioned, the more potential to help just about anyone having the same problem, regardless of their setup.
How exactly do I configuring the Node-Red Home Assistant server URL with hassio? I’m trying to access the node red webpage though can’t because of duckdns.
So I can now acess my HA through the IP:8123 and also XXXX.duckdns.org (using ssl with nginx). Though Ive tried everything to access the node red UI with no luck. I have port 80 and 443 forwarded. Any ideas on whats happening?
Sure! I learned how to do it from an article on the DIY Futurism blog. I linked to the article in the third post in this thread. Scroll down the blog post to the “Routing Traffic Locally” section. It shows you what you need to add to the “hosts” configuration setting.
“Neither of those options were available to me, but I am running Pi Hole. Since Pi Hole is acting as the DNS server for my local network, I can add a custom host entry for my domain name. Now, all the clients on my LAN will resolve hass.mydomain.com to the private IP instead of the public one:”
Sorry to hijack this thread from last year, but I’m trying to do this same thing but I’m working with HA and Node-RED and LetsEncrypt in Docker containers.