Unable to authenticate on new mobile app

I just recently updated the mobile app and followed the instructions to remove my phone’s integration from HASS and then log back in.

Everything is fine up until I sign in in the web view. After an apparently successful login, the web view goes away and I’m met with a dialog that say “You must sign in to continue”, “The server has rejected your credentials and you must sign in again to continue”. I get this on a loop.

I’m able to log in via any mobile browser or desktop. When I do, I can see that refresh tokens have been generated for each session, so I’m confident that I’m logging in just fine, but the app isn’t passing the right token.

I’ve tried updating HASS to the latest (114.0) and uninstalling and reinstalling the HASS Companion app on my phone, but no luck.

The only thing that shows in my log is WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from <IP of my reverse proxy>.

I’ll try on a different iOS device on iOS 13, but I figured I’d see if anyone else had a similar issue first.

Just verified that this also effects my iPad on iOS 13.6. So not beta related.

Ok, seems to be something to do with my Caddy reverse proxy. I’m not sure what is causing the authentication to be rejected by the server now though when it was working prior to the update and authentication through Caddy works just find in any web browser, including on iOS Safari.

Workaround found… I logged and ran setup using the IP address to skirt around the proxy and then after loading up HASS, I updated the URL back to the proxied one and things work fine.

1 Like