Welcome to today’s daily kōrero!
Anyone can make the thread, first in first served. If you are here on a day and there’s no daily thread, feel free to create it!
Anyway, it’s just a chance to talk about your day, what you have planned, what you have done, etc.
So, how’s it going?
Mine is a docker container on Unraid. I encountered a similar issue once with reverse proxy. I had to use the use_x_forwarded_for and trusted_proxies flags in the configuration.yaml. Can see the options here: https://www.home-assistant.io/integrations/http/
Not sure if it’s exactly the issue you’re having though.
I’m not using a reverse proxy currently. Just IP:port, which worked yesterday but suddenly doesn’t work today :(.
As far as I can tell, there hasn’t been an update since last week on the stable branch, so I’ve got no idea what’s changed.
There should be something in the logs hopefully to track down the problem
There wasn’t when I first checked, but now I’ve got loads of:
WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authenticationI’ve found lots of posts about this issue, but they are all related to using a reverse proxy. I’m not using one :(
Weird you think clearing browser cache or different browser works?
I can’t remember if I had the reverse proxy setup when they made the change to requiring trusted_proxies. But I do know I had to add in the IP address of the server it’s running on as trusted
I had previously tried restarting the home assistant container, and had cleared my browser cache, and no dice. But now I’ve rebooted the whole server and now it seems to work. So now back to my original task of creating a template 🙂