I updated to the latest version it broke my reverse proxy. I am using letsencrypt add on. THis is my config
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
use_x_forwarded_for: true
trusted_proxies:
- 127.0.0.1
- 192.168.10.0/24
What did I miss?
I have tried putting the subnet without /24 too
Did you get any error logs regarding reverse_proxy?
No, someone else said the same thing but there is no log under configuration > logs
See first post from here-
Hi
With the latest update of home assistant v2021.7.0 I started getting “400 Bad Request” error when I tried to access HA via my external http/https address. I could still access home assistant without error via the local IP address.
If you check out the breaking changes if you are running a proxy you need to add
http:
use_x_forwarded_for: true
trusted_proxies:
- XXX.XXX.XXX.XXX # Add the IP address of the proxy server
Reference - HTTP - Home Assistant
However it still didn’t work …
Edit: Wrong link.
Tried that already. Portainer doesn’t show me the option “compose_default” under networks. It doesn’t show my any containers under the container lab either. I definitely have 6 addons running.
Can you try using 172.30.33.0/24
in the trusted_proxies
?
There are definitely logs for home assistant.
koying
(Chris B)
July 25, 2021, 10:50am
9
But what are you using for the reverse proxy functionality?
If you actually mean the letsencrypt addon, it just manages certificates…
Where you have compose_default, I have hassio
edit: screenshot
Click hassio network it will have the relevant ip address