Unexpected error when logging in with latest browser extension - 404 on /identity/accounts/prelogin/password

[Amamiya23]

Subject

Unexpected error when logging in with the latest browser extension (Chrome).

Deployment method

Docker (vaultwarden/server:latest)

Steps To Reproduce

1. Use the latest Bitwarden browser extension (Chrome)
2. Attempt to log in to the self-hosted Vaultwarden instance
3. Login fails with an unexpected error

Expected behaviour

Successful login.

Actual behaviour

Login fails. The server returns a 404 for the prelogin endpoint.

Logs

[2026-05-30 03:12:37.057][request][INFO] POST /identity/accounts/prelogin/password
[2026-05-30 03:12:37.057][response][INFO] 404 Not Found

Environment

• Browser: Chrome
• Docker image: vaultwarden/server:latest

Additional context

The endpoint /identity/accounts/prelogin/password returns 404, which suggests the latest browser extension is calling a new API route that Vaultwarden has not yet implemented.

[BlackDex]

Update to the latest version first, as is requested in the issue template.

[BlackDex]

You can subscribe on the releases notifications on this repo.
But, the breaking change came from Bitwarden. And, if you would have updated every restless of Vaultwarden, the chance of this breaking would have been very low.

That doesn't mean it can still happen in the future of course.

[LeoLTM]

I am using vaultwarden inside an Proxmox LXC container via Proxmox VE helper scripts. Even after updating to >=1.36.0, this error persists:

Network logs:

Filename: /identity/accounts/prelogin/password
Status: 404

[stefan0xC]

You are using a third party script that is apparently unreliable and more importantly unsupported by Vaultwarden. If the error persists you did not upgrade to the latest release.

[nillpoe]

@LeoLTM Proxmox VE helper script update didn't work for me either. I had to backup the data and re-install it (though it's inappropriate to ask here)

[LeoLTM]

@LeoLTM Proxmox VE helper script update didn't work for me either. I had to backup the data and re-install it (though it's inappropriate to ask here)

Ok thanks that's great to know! Will try the same.