I'm trying to configure home assistant so that it can be accessed from anywhere in the internet. Right now I have it port forwarded on port 8123, and that works fine, however I can't get https with ssl to work with that. I want to use my domain and reverse proxy with nginx to get ssl working, because from the internet to the nginx server has ssl working great already. When I setup the reverse proxy to route domain.net/ha to my server at port 8123, after I enabled reverse proxy in the ha config, it says 404: Not Found. What I need to see is that my nginx proxy is working correctly and not routing traffic to my home assistant server with the path /ha. How can I see home assistant's http access log like I can in apache or nginx? I can't seem to find it anywhere.
#I need a home assistant http access log
1 messages · Page 1 of 1 (latest)
I'm trying to set up nginx to route domain.net/ha to the ha ip address at its root. when I forward it to my webserver, it does exactly that, so I can't seem to figure out the problem
what do you mean? My domain is port forwarded to my nginx server running as a reverse proxy. When it sees /ha, it forwards that to / at the ha ip address
I mean
you can't do that
Why can't I do that?
HA shouldn't need to support anything. nginx is working as a reverse proxy, so to HA it should just look like a local client is connecting at the home assistant root path
And sadly NGINX can't rewrite all the client side UI content
The way many modern webapps work causes problems like this. It's a well known "problem" with HA's frontend, and has been for years
You have to choices:
- Pick a different port for HA
- Pick a different hostname for HA
I still don't understand the problem or how doing those two things would help
The problem is you can't use /ha (or anything else) in NGINX
So, you either use a separate hostname (and map it directly) or a separate port (and map it directly)
Can you explain why?
And sadly NGINX can't rewrite all the client side UI content
The way many modern webapps work causes problems like this. It's a well known "problem" with HA's frontend, and has been for years
There's some forum threads and GitHub issues that go into it in more detail if you want more about why
Why is largely irrelevant though
Create a cname and use ha.domain.net etc?