Hi. I have the NGINX Home Assistant SSL Proxy add-on installed and work correctly. Now I see that there is also a NGINX Proxy Manager add-on. I am not clear what is the difference between the two, and whether they are complementary or not.
came here with the same question, didnât find an answer though @zefoto did you end up switching to proxy manager add-on?
the reason I came across this was because i need to setup an addition custom location for externally accessing another locally hosted website which uses the same 443 port.
not sure if that is possible with the ânginx Home assistant SSL proxyâ add-on
The answer is a no - at least not to my knowledge.
With the ânginx Home assistant SSL proxyâ add-on, along with DuckDNS add-on, you would be able to expose you HA to the internet. The intension here is to get it up and running with minimal user configuration.
And if anyone (like you) wants a step further, to expose additional locations to the internet, then you probably would go with the NGINX Proxy Manager (or Caddy, FWIW) add-on. Obviously more tweaking would be required. Search around you probably would find more discussions.
Could the NGINX Proxy Manager handle LetâsEncrypt DNS-01 challenge these days? I didnât check for a while now.
thanks
I have tried both with the nginx ssl add-on and the nginx proxy manager. I think the specific use case I need wouldnât work without manually modifying the configuration files. though I havenât been able to make it work either ways
To do so, you would want to look into the other âNginx Proxy Managerâ community add-on. Similar stack, but with more capability.
Certainly you could also try to roll your own reverse proxy, maybe in a container you manage yourselves, for Apache, Nginx, or Caddy.
Or maybe look into Cloudflare? There is also an add-on for that. The upside is that you donât even need to open any port on your router⌠but the downside (?) is that you would need a domain name, which typically would cost you some.