You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not entirely sure, but I think you have to do this if HA is running in Docker or in some other situation where it has to go through NAT to get to the Wifi or LAN to which the host is connected. Might be worth a mention in the setup instructions.
Other than that, the proxy manager worked really nicely for me. Thanks for this work!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
After following the setup instructions, I got the error above when trying to access my HA via the reverse proxy. The solution was to add the use_x_forwarded_for and trusted_proxies options to the http section in configuration.yaml, as described here: https://community.home-assistant.io/t/home-assistant-400-bad-request-docker-proxy-solution/322163.
I'm not entirely sure, but I think you have to do this if HA is running in Docker or in some other situation where it has to go through NAT to get to the Wifi or LAN to which the host is connected. Might be worth a mention in the setup instructions.
Other than that, the proxy manager worked really nicely for me. Thanks for this work!
Beta Was this translation helpful? Give feedback.
All reactions