Vaultwarden admin password

[andyw73]

I have run the script bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/vaultwarden.sh)" and set the vaultwarden admin token. This is seen in /opt/vaultwarden/.env and is converted to ADMIN_TOKEN='$argon2i$v=#######'. I am unable to login to the admin panel with set password and receive a Error: Invalid admin token, please try again.
Has anyone else run into this issue?

[tteck]

Please utilize the password you entered during the "Set the ADMIN_TOKEN" process.

[chaot2000]

Same here. I used the script to update - all are fine.

Changing Admin Token - always the same error message "Error: Invalid admin token, please try again."

[tteck]

Upon retesting, I entered "password" on the "Set ADMIN_TOKEN" screen. I then proceeded to IP:8000/admin and entered "password" without encountering any issues. (tested 3 times, changing password each time)

[chaot2000]

I've got a brand new Installation from Vaultwarden. This solved the ADMIN_TOKEN problem.

But, i can't import the password from my old instance. Error comes up with

"Cannot read properties of null (reading '0')"

it's really annoying

[Node815]

Did you export from CSV by chance? If so, try using the JSON export method if you can. I use the DOCKER version of Vaultwarden (testing release) and had to rebuild my server a few weeks ago, and it failed to restore from the CSV to the same version, but JSON worked perfectly fine. Also, Vaultwarden just released 1.3.0 today to stable branches which I think now supports the much awaited Passkey support.

[chaot2000]

@PDXUser thanks for the hint.

After reinstalling with the ingenious script, I was unable to import a .JSON. With CSV it worked afterwards.
I have now successfully moved everything!

Many thanks for your support!
Closed from my site

[daschmidt1994]

is there already a solution?
Have the same problem if i try to change the password

[andyw73]

In my case there was an extra admin token located in /opt/vaultwarden/data/config.json. I commented out the "admin_token" using nano and re run the script. I was then able to login to the admin panel again. Hope this helps anyone else facing this issue.

[navels]

In my case there was an extra admin token located in /opt/vaultwarden/data/config.json. I commented out the "admin_token" using nano and re run the script. I was then able to login to the admin panel again. Hope this helps anyone else facing this issue.

Thanks, same.

[navels]

Got a repro for this problem:

1. Delete the admin_token from /opt/vaultwarden/data/config.json
2. Set the admin token using the update script, which writes it to /opt/vaultwarden/.env.
3. Log into the admin panel using the new token
4. Click Save in the admin panel

This causes the admin_token to be saved back to /top/vaultwarden/data/config.json`. At this point the same token is in both files.

6. Change the admin token with the update script.

At this point the token in the two files are different, with the older token taking precedence when logging into the admin panel.

[navels]

@tteck fyi discussing this wonky (imo) behavior of vaultwarden's over here: dani-garcia/vaultwarden#4758

[navels]

I'm waiting to see what the vaultwarden folks say but I'd be inclined to have the update script set the token in both places (.env and data/config.json). I can submit a PR if you like.

[andyw73]

The reason most people would want to change their password is due to being lost or forgoten. I agree with Navels the script should check the existence of both locations and change both locations accordingly. It seems counter intuitive that the password will only be changed in one location as, most will have been in the admin panel to change various parameters according to there setup.

[navels]

@andyw73 thanks and if you want to add this to the vaultwarden discussion: dani-garcia/vaultwarden#4758

[tteck]

commit cfa1b2e fixes issue

[navels]

Confirmed that fixes it, thanks!