I could do with some very brief help with using /configuring the official NGINX Home Assistant SSL proxy add-on.
currently I use the http component to use SSL and the Duckdns add-on to get/store a certificate .
I’ve read a few threads on the forum regarding benefits of using a reverse proxy instead of the http component however I wonder if I will use some of those benefits and therefore is a reverse proxy required.
currently I have a nextcloud server on another server which uses port 443 and 80 for access , home assistant uses 8123 which is great as they never conflict .
I would eventually like to setup a wall tablet to access home assistant locally hence the interest in the reverse proxy.
If I setup the Nginx add-on and use the cert from the Duckdns add-on ,
can I configure the router to still forward port 8123(external) but this time to 443(internal) instead of the current 8123 to 8123. Do I need to forward port 80 as well or can I leave that out ?
Do I need to add
use_x_forwarded_for: true(can some one explain what x forward for means ?) and
trusted_proxies:127.0.0.1Is this all to prevent home assisant being available on http:// on the domain name and only allow use of the proxy ? also do I need
This thread suggests that if you dont filter URL’s or require authentication then there is not much benefit to a reverse proxy , is this possible with this add-on ?
I take it I can whitelist IP’s on the local network to not use the login credentials via the http component (i.e for the wall mounted tablet)
any other advice regarding this add-on would be greatly received
thanks in advance