Unable to reset authentification!

Hi

Having some issues with some external components using HA identification, I wanted to make it clean but I failed ! As stated here https://www.home-assistant.io/docs/authentication/ I have stopped HA, deleted the auth, auth_provider.homeassistant files (no onboarding file on mine), deleted cookies in my browser and restarted HA !
Now all I have is that and if I click on Start Over, nothing happens ! Tried too with a different browser but same !
halogin
I commented out also in my config file these:

#http:
#  trusted_networks:
#    - 127.0.0.1
#    - 192.168.1.0/24

What is going wrong here ?

Thanks

Vincèn

You shouldn’t comment out http:

That might be why - make sure you restart HA if you change config

If I don’t comment it, I get the choice of user at login page but none user avalaible in list :frowning:
halogin

It still thinks you have trusted networks set for auth. Look in config file for trusted networks.

See here - https://www.home-assistant.io/docs/authentication/providers/

I bet you have auth providers set. Remove that section and it will onboard you again and you can add it back.

Oups sorry to have missed that ! So I commented out both the http//trusted_network section and the auth_providers one, removed the auth* file in .storage ! But now it asks me directly to login without any way to create an account or let me in directly…

Do you have anything in the auth providers section? Comment all that out

Well all I have is that and it’s all commented out now but still no way to get access, it still asks to login :frowning:

#  auth_providers:
#    - type: trusted_networks
    
#http:
#  trusted_networks:
#    - 127.0.0.1
#    - 192.168.1.0/24

Don’t comment out http!

In config/,storage is there an on boarding file? Possibly delete that so it onboards you again…

with http still the same it asks to login straight :frowning:

no onboards file ! I deleted again the auth file that is created again at each restart of HA but I noticed a hassio file that contains that:

{
    "data": {
        "hassio_user": "5a273591d0be4b1ebca7cb12c316426f"
    },
    "key": "hassio",
    "version": 1
}

It looks to be related to authentification too ! Should I delete it ? no risk ?

I would…

I think you can delete all auth*.* and hassio and onboarding… don’t delete lovelace or any core files…

Tried that yesterday already and not much more success, killing my head on that !! But my hassio system is perhaps too the issue !! As I have no way to control HA in hassio (without web access to it), my only way to do that is delete files through the samba share and immediately restart HA by power cycling but HA is still running while doing it…

Pfiu start to be so bored of that problem and the pain in the ass hassio is when you have any problem :frowning:
As advised by Tinkerer on discord, I went by the terminal way but not much better !! Login physically on pi as root, get hassos prompt so you can stop ha before deleting files ! Unhappy when you stop ha it stops too the samba share :rage: so wanted to delete files from console but no way to find out how to access prompt of host os :frowning: login command is not working well not giving access at console of host os…

Make sure you also have type: homeassistant under auth_providers or it won’t let you register an initial user.

Isn’t is supposed to be included by default if nothing is listed ?

Yes it’s default. You could try creating an api key and login with that, then delete users maybe

You shouldn’t be using that

Correct, however it looks like op wants to include trusted network auth and is adding the auth providers section so defaults won’t apply?

I have given up on that problem (see other thread about it) as it’s crazy and discovered it’s impossible to reset the auth system of HA if you loose master password of it !! Very nice design and only way is to restore a backup on a fresh new install :frowning:

no it’s not. I have reset mine 3 times

How ? considering I never succeeded on mine (I kept memory card as is just in case to test some other way to reset it :wink: