this post was submitted on 31 Aug 2023
9 points (90.9% liked)
Aotearoa / New Zealand
1658 readers
27 users here now
Kia ora and welcome to !newzealand, a place to share and discuss anything about Aotearoa in general
- For politics , please use !politics@lemmy.nz
- Shitposts, circlejerks, memes, and non-NZ topics belong in !offtopic@lemmy.nz
- If you need help using Lemmy.nz, go to !support@lemmy.nz
- NZ regional and special interest communities
Rules:
FAQ ~ NZ Community List ~ Join Matrix chatroom
Banner image by Bernard Spragg
Got an idea for next month's banner?
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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 🙂