Update your router, point your external port to the 192.xxx.xxx.73 (IP of the HAOS), and to the port per the configuration inside your NGINX Home Assistant SSL proxy add-on
Use https and the DuckDNS domain name to connect to HA, for when you are outside,
Use http and the .73 IP and port 8123 to connect to HA if you and HA are on the same LAN.
And then follow your Google Home setup guide, which is outside of the scope of this thread.
Edit: adding step 6 - 8 above.
===
I’d recommend this, because of the intension you outlined the other day:
This NPM add-on is probably not a good fit for you / your setup.
I know what you said, but if nothing works, would seriously recommend Nabu Casa.
Can I still use the DuckDNS add-on in conjunction with this? I want the DuckDNS add-on to keep my public IP up-to-date on duckdns.org. The DuckDNS add-on also generates Let’s Encrypt certs, but it appears I don’t need those with NGINX Proxy Manager?
Is it possible to point NGINX Proxy Manager to the same certs generated by the DuckDNS add-on?
Or, if not using the DuckDNS add-on certs, how do I set up NGINX Proxy Manager to auto-renew expiring certs like the DuckDNS add-on? Does it even have that capability?
I’m asking all this because I recently started getting emails that my Let’s Encrypt certs are expiring in a few days… so I checked the DuckDNS add-on and those certs indicate they are good until April… then I checked the certs for NGINX Proxy Manager and, based on the dates, all of them are expired as of a few months ago… However, I haven’t had any issues accessing the sites/services… so I’m not understanding what certs NGINX Proxy Manager is even using.
This is a great add-on.
Question - is there a reason why the “streams” host option is not available, unlike the docker version?
I am hoping to configure TCP & UDP port forwarding for a game server in NPM instead of in my router.
Screenshot of the dashboard at nginxproxymanager .com:
I have a feeling that you are at the wrong place. This thread is about the community add-on Nginx Proxy Manager, and what you discribed above is about the official add-on NGINX Home Assistant SSL proxy. These 2 add-ons both use NGINX, but vastly different.
Regarding your issue, recommended you start a different thread, check the logs on both Lets encrypt and NGINX Home Assistant SSL Proxy
Hello all,
there are regular security updates for Nginx. The addon itself has not been updated for a while. Does this mean that the NGINX version of the addon is also outdated and has security vulnerabilities? How can I manually update the nginx component?
Hey @frenck, the login data inside my mariadb instance is corrupted making it impossible for me change the password (and other weird behaviour). I’ve hit the “reset” toggle for the addon which clears all my settings with the exclusion of the login details.
Are you able to extend the “reset” functionality to clear all NGINX Proxy Manager settings inside MARIADB including the login details.
As far as I’ve progressed I am clueless on how to fully wipe the mariadb and start from scratch…
I found a workaround to let the renewal process work but which only lasts until the add-on is restarted (and thus is not an actual fix). You’ll still have to do this every 3 months, but it beats having to nuke your entire SSL setup and re-do every cert and every proxy host every 3 months.
Console into the addon_1234abcd_nginxproxymanager container as root, I use portainer to allow me to do this. The Home Assistant devs have bent over backwards to try and prevent you from accessing normal container controls which doesn’t seem like a great use of anyone’s time. You’ll have to sort out how to make that happen for you, and the result will likely be a hilarious “unsupported installation” message for your efforts.
Kill the stuck certbot instance that ran at container start and won’t complete due to the change required below: pkill certbot
Remove the offending line from letsencrypt.ini: sed -i 's/authenticator = webroot//' /etc/letsencrypt.ini
And that’s it! CF renewals will now work until you restart the container. This has been fixed in the upstream project for over a year now, hopefully we’ll see some of those fixes make their way into the Home Assistant add-on some day.
I’m currently using traefik on an external vm and thinking of switching to this. the only thing stoping me is tcp routes.
In my setup traefik handles the certs for mqtt as well (native port not websockets), how can i replicate it with NPM as it does not support tcp
Hello, everyone. I installed and set up the Nginx Proxy Manager with Home Assistant.
So far everything works, if I call the xxx.duckdns.org address, the login window comes from the access
After I entered the access data. Am I on my Home Assistant page.
Problem 1: As soon as I make a few clicks, he immediately wants me to log in again (Access List Nginx Proxy Manager).
Problem 2:
When I switch to the Settings/Integrations page and want to set up Octoprint, for example, I get the following error:
If I remove the access list in the Nginx Proxy Manager, everything works fine. With Access List this error occurs every few minutes. It makes no difference whether I use the Homeassistant Android app or the Chrome browser on my cell phone or computer.
With nginx Proxy manager my external address for HA is https://yyy.xxx.duckdns.org
There is an additional subdomain in front and the port is not neccessary!
For everyone who is running into the INTERNAL ERROR issue, just choose “use DNS challenge” and put your DuckDNS token in, takes me several days to find out.
hope this will save your time
