I can access all my containers as subdomains except one, homeassistant.
h t t p s / / homeassistant . XXXXXXXXXXXXX . duckdns . org gives me;
“502 Bad Gateway, nginx/1.16.1”
As there is already a provided “homeassistant.subdomain.conf.sample” I figured I don’t need to edit it, I just removed the “sample” part an started the container again.
I can’t tell if the 502 message is due to something wrong/missing in my nginx container, or if it is from the Home Assistant conatiner.
Perhaps it’s only nginx related.
The homeassistant.subdomain.conf reads;
“# make sure that your dns has a cname set for homeassistant and that your homeassistant container is not using a base url”
So, too make sure that I’m not using a buse url, I look into my “configuration.yaml” in the Home Assistant cantainer;
No matter what I edit, I still gate the 502 gateway.
Configure a default setup of Home Assistant (frontend, api, etc)
Uncomment this if you are using SSL/TLS, running in Docker container, etc.
For extra security set this to only accept connections on localhost if NGINX is on the same machine
Update this line to be your domain
You must set the trusted proxy IP address so that Home Assistant will properly accept connections
Set this to your NGINX machine IP, or localhost if hosted on the same machine.
The trusted proxies IP address, should that be my “192.168.1.XXX”, “localhost”, “127.0.0.11” or the nginx docker container’s IP?
Sorry for this confusing post, but it reflects how I feel…