Password recovery not working for me

I have tried to recover from a missing password (Hass decided to reauthenticate after upgrading, I hadn’t stored password in password manager, roast me if you like). So I followed the instructions.

But I am presented again with the login page.

Tried to use another browser, incognito mode, another OS. Tried to move out of the way .storage altogether, looking around in the forum, in Reddit, in the web…

I am a bit frustrated. I am locked out of Hass and the documented method for recovery doesn’t work.

Any hints?

Thanks!

Follow those steps but when you load the page refresh the cache as well. (Ctrl+f5)

I tried that. I did it again just to be sure. I also tried to connect using a browser that hadn’t previously connected to Hass, and got the same login page again.

How can I gather more data? The log doesn’t have anything.

If you’re still getting a log in page then you didn’t do something correctly. You deleted the following files from the hidden .storage folder (when home assistant is OFF):

  • auth
  • auth_provider.homeassistant
  • onboarding
  • hassio
  • cloud

Yes, that is what I did. From my history:
330 sudo rm auth auth_provider.homeassistant onboarding cloud
This is a docker install, and there is no hassio file on it.
Then I restarted (also tried to repeat the procedure and reboot instead of restart, same result).
I have enabled logging in configuration.yaml:
logger:
But it doesn’t log anything at all.

Did you verify that sudo rm was removing the files? I’ve seen issues where rm does not remove hidden files. While these files are not hidden the folder you are in is.

Yes, I did. Here is the current content of the folder:

pi@hass1:~ $ ls -la homeassistant/.storage/
total 80
drwxr-xr-x 2 pi   pi    4096 Jan  7 17:15 .
drwxr-xr-x 6 pi   pi    4096 Jan  7 18:02 ..
-rw-r--r-- 1 pi   pi     588 Nov 24 12:07 core.area_registry
-rw------- 1 pi   pi     278 Nov 23 20:05 core.config
-rw-r--r-- 1 root root  4330 Jan  7 08:51 core.config_entries
-rw-r--r-- 1 root root  3940 Dec 17 17:33 core.device_registry
-rw-r--r-- 1 pi   pi   11533 Nov 27 08:40 core.entity_registry
-rw-r--r-- 1 root root  3871 Jan  7 16:49 core.restore_state
-rw-r--r-- 1 pi   pi     168 Nov 24 11:39 frontend.user_data_a8196b6fdeef4130ba4b3c042bb3b8ae
-rw-r--r-- 1 root root  8369 Jan  3 18:55 lovelace
-rw-r--r-- 1 root root 12433 Jan  7 09:47 mobile_app
-rw-r--r-- 1 pi   pi     315 Nov 23 20:04 person

If home assistant is off (Docker container is stopped) and you deleted those files, then it should be working. After you start home assistant, do those files come back?

Also, you could backup all those files. Stop home assistant. Delete the whole .storage folder. Start home assistant. Create log in. Stop home assistant. Replace all those files that were backed up. Start home assistant and log back in.

I did try to move .storage out of the way altogether:
pi@hass1:~ $ sudo service home-assistant stop && mv homeassistant/.storage homeassistant/storage-outoftheway && sudo service home-assistant start
The result is that Hass does start, it does not create a new .storage folder as I had expected:

pi@hass1:~ $ ls -la homeassistant/.storage
ls: cannot access 'homeassistant/.storage': No such file or directory

But it does get me to the fine login page again :frowning:

and the login page does not have a log in with 2 password positions?

Nope, it has this:
56

Is there any route I could try to specifically go to the first user page? Perhaps it is just that it is redirecting me to the wrong page (login instead of first user)

I don’t know what the actual url would be. Sorry. What version of HA are you running?

Just updated to 103.6

I don’t know. I’m stumped. It should be working. Sorry I couldn’t help.

Thanks for trying!

It seems that the home assistant directory has moved from homeassistant/ to .homeassistant/ and therefore my changes were being duly ignored.

Still scratching my head, but at least making progress. Now, thinking of salvaging what I can of my configuration…

Well, you should be able to salvage it all, just do the steps in that previous link and you should be good to go. But it totally explains why it wasn’t working. And you aren’t crazy. So that’s a good thing

1 Like