I have a working HASS setup on a RPi, running 0.118.2. I have used the standard guide for setting up DuckDNS and a NGINX reverse proxy, which are both installed via the supervisor as addons. This all works perfectly for remote access to my Home Assistant. (And setup was impressively easy!)
I also have another app installed on a different server, available only on my internal home network on HTTP. I’d like to securely access this app externally, without using HTTP.
Seeing as NGINX is working so well, and all the certs and stuff are already setup, I’d like to configure NGINX on HASS to handle reverse proxy-ing for that additional app.
- when I hit https://externalurl:8123/ it will reverse proxy me to http://192.168.0.50:8123/ (This is for HASS)
I’d like to maintain this, but also add:
- when I hit https://externalurl:4321/ it will reverse proxy me to http://192.168.0.40:4321/ (This would be for the other app)
Looking at the documentation on the addon, it looks like I could be trying
customize.active=true. However I don’t currently have anything in my /share directory.
Should I set
customize.default="nginx_proxy_default.conf"… then create that file and fill it out as per standard NGINX documentation?
Most importantly, if I do this, will it overwrite the existing config and break my existing reverse proxy?
Any and all help is appreciated!