After hasing admin password unable to login into the /admin page. #1641

New Issue

MrUnknownDE · 2026-04-06T02:06:29+02:00

MrUnknownDE commented

2026-04-06 02:06:29 +02:00

Originally created by @sebasdt on 4/16/2023

Subject of the issue

After I changed my admin password to a more secure password, my vaultwarden instance is still saying I need to secure it.
This also resulted in me not able to log into the admin page.

Deployment environment

I'm using portainer and vaultwarden has its own bind volume for saving everything persitantly.

vaultwarden version:
Latest stable version: 1.28.1

Install method:
portainer (docker stack)
Clients used:
Reverse proxy and version:
MySQL/MariaDB or PostgreSQL version:
Other relevant details:
Looking into the vaultwarden volume I dont see a config.json that could conflict with the docker env's

Steps to reproduce

Set up Vaultwarden with plain text admin token

After Vaultwarden is up and running with plain text token, generate a hashed token with argon2

Change ADMIN_TOKEN to hashed token and restart Vaultwarden

Vaultwarden logs warning about using a plain text token with ADMIN_TOKEN set to a hashed token

Expected behaviour

Im able to log into the admin page and that the logs dont show I need to switch to a more secure password

Actual behaviour

The /admin page is saying: "Error: Invalid admin token, please try again." and not letting me log in.

Troubleshooting data

Logs
[NOTICE] You are using a plain textADMIN_TOKEN` which is insecure.

Please generate a secure Argon2 PHC string by using vaultwarden hash or argon2.

See: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page#secure-the-admin_token
`

docker-compose yml admin env:
NOTE THIS IS NOT MY TOKEN BUT IT DOES LOOK LIKE THIS!
environment: ADMIN_TOKEN: $$argon2id$$v=19$$m=19456,t=2,p=1$$UUZxK1FZMkZoRHFQRlVrTXZvS0E3bHpNQW55c2dBN2NORzdsa0Nxd1JhND0$$cUoId+JBUsJutlG4rfDZayExfjq4TCt48aBc9qsc3UI

*Originally created by @sebasdt on 4/16/2023*   ### Subject of the issue  After I changed my admin password to a more secure password, my vaultwarden instance is still saying I need to secure it. This also resulted in me not able to log into the admin page. ### Deployment environment I'm using portainer and vaultwarden has its own bind volume for saving everything persitantly.     * vaultwarden version: Latest stable version: 1.28.1  * Install method: portainer (docker stack) * Clients used:  * Reverse proxy and version:  * MySQL/MariaDB or PostgreSQL version:  * Other relevant details: Looking into the vaultwarden volume I dont see a config.json that could conflict with the docker env's ### Steps to reproduce  - Set up Vaultwarden with plain text admin token - After Vaultwarden is up and running with plain text token, generate a hashed token with argon2 - Change ADMIN_TOKEN to hashed token and restart Vaultwarden - Vaultwarden logs warning about using a plain text token with ADMIN_TOKEN set to a hashed token ### Expected behaviour  Im able to log into the admin page and that the logs dont show I need to switch to a more secure password ### Actual behaviour  The /admin page is saying: "Error: Invalid admin token, please try again." and not letting me log in. ### Troubleshooting data  Logs ` [NOTICE] You are using a plain text `ADMIN_TOKEN` which is insecure. Please generate a secure Argon2 PHC string by using `vaultwarden hash` or `argon2`. See: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page#secure-the-admin_token ` **docker-compose yml admin env:** NOTE THIS IS NOT MY TOKEN BUT IT DOES LOOK LIKE THIS! ` environment: ADMIN_TOKEN: $$argon2id$$v=19$$m=19456,t=2,p=1$$UUZxK1FZMkZoRHFQRlVrTXZvS0E3bHpNQW55c2dBN2NORzdsa0Nxd1JhND0$$cUoId+JBUsJutlG4rfDZayExfjq4TCt48aBc9qsc3UI `

MrUnknownDE closed this issue

2026-04-06 02:06:29 +02:00

MrUnknownDE referenced this issue

2026-04-06 03:46:05 +02:00

Updated branding, email and crates #2481

MrUnknownDE referenced this issue

2026-04-06 03:46:06 +02:00

Updated admin logo and fix smtp tls. #2484

Sign in to join this conversation.