#Unable to use the remote access link to log into my instance on desktop, but works through the app

1 messages · Page 1 of 1 (latest)

formal fossil
#

Like the title says. I can access my instance just fine through the mobile app, but as soon as I try to use the link that Nabu Casa provides me to access my instance through a browser (I tried Firefox, Brave, and Chrome), it shows a log message on my instance saying that there was an invalid login from localhost. It's generated by the homeassistant.components.http.ban module, and it's complaining about invalid auth.

I've used both the username and password for my instance and my nabu casa account with the same error, thinking there's something weird with it. I changed my password and relogged into the mobile app correctly, but through a browser it still says the same thing.

I'm at a loss as to why it's not working.

ruby vault
#

Do you have some other auth providers configured in configuration.yaml

formal fossil
#

I signed up for the nabu casa subscription, set it up in my instance and the app, and went with that. I didn't touch any YAML files, and I only noticed that it didn't work through the browser today when I was trying to show my coworkers what it was.

ruby vault
#

You're entering the HA username and password when using the URL in a browser?

#

The Nabu Casa account is not created as an HA user account

#

Can you sign in using the address in a browser on your phone data, but not your work network?

formal fossil
formal fossil
ruby vault
#

Do you have more than one HA server using the same Nabu Casa account?

#

When connected locally, do you see multiple entries for Home Assistant at Settings > System > Network > SSDP browser?

formal fossil
#

I only have the one HA server

formal fossil
#

So I made a temp user and an easy password, and it let me log in with that. I went back and reset the password for my account to a passphrase instead of generating one through Google's password generator, and that let me log in without issues. Either I'm dumb or the password that was generated both times before had something that it didn't like for whatever reason. Maybe it was a different character that I couldn't hit with my keyboard?

ruby vault
#

Sounds more like password just didn't match?