Vaultwarden having problems Recognizing Master Passwords

[NxckyBear]

Vaultwarden Support String

I dont have any support string as I did not set up an admin page yet due to above problem

Vaultwarden Build Version

v1.33.0

Deployment method

Official Container Image

Custom deployment method

original way how to install (base: sqlite) and with another database (pgsql)

Reverse Proxy

caddy 2.9.1

Host/Server Operating System

Linux

Operating System Version

Ubuntu 22.04 Jammy

Clients

Web Vault, Browser Extension, iOS, Desktop

Client Version

Brave 1.74.38 (PC), Bitwarden Extension, Bitwarden mobile client

Steps To Reproduce

1. start vaultwarden (docker base image)
2. go to the web vault
3. create new user and log in (you should enable sight on your password and copy it for best results)
4. log into the bitwarden extension or mobile client (self hosted)
5. you will see error

Expected Result

You actually should successfully log in everywhere

Actual Result

You can log in on the web where you created your user, you are not able to log in anywhere else, due to it saying that your username or password is incorrect

Logs

`[2025-01-27 22:02:50.674][request][INFO] POST /identity/accounts/prelogin
[2025-01-27 22:02:50.674][response][INFO] (prelogin) POST /identity/accounts/prelogin => 200 OK
[2025-01-27 22:02:50.810][request][INFO] POST /identity/connect/token
[2025-01-27 22:02:50.810][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: <ip>. Username: <username>.
[2025-01-27 22:02:50.810][response][INFO] (login) POST /identity/connect/token => 400 Bad Request`

Screenshots or Videos

No response

Additional Context

I have lastly tried to move vaultwardens backend to pgsql, which is basically where everything started... It worked fine before that...
However I reinstalled everything, new docker container, new files, however this did not fix anything.

[BlackDex]

I just tested it on my phone, and it works without issues.
Maybe your reverse proxy or tunnel provider or something else in between, like browser add-ons are causing issues.

[shadowjig]

I had this same issue happen to me. I restarted the container and it worked fine. I also had enabled web sockets in nginx proxy manager and decided to turn that off again. So it was either or both of those issues.

[BlackDex]

Websocket has nothing to do login in that sense, so probably just the restart which triggered some docker components i think.

[NxckyBear]

Restarting the container does not fix that issue in any way, I restarted the container several times and even killed it and then started, also tried recreating it, without success
How should my reverse proxy be an issue here? I do not get a 502
I get the error that my password should be wrong which is untrue

[BlackDex]

To be fair, if it was untrue, you would have been able to login
Maybe start with showing how you configured it and how you start and stop the container.

And try to enable the admin interface so you can get the support string and other useful information like how many and which users are there.

[NxckyBear]

I copied the password at account creation and pasted it in the bitwarden extension and get that error. So yes it IS untrue
I literally just copied the docker base command for starting vaultwarden, and deleted everything for a fresh new start of vaultwarden

I use Portainer for managing the containers

if the admin interface helps me with logging in with something else than a password, then sure I might go for that.

I also added the sqlite database where all the data is stored as env DATABASE_URL to avoid conflicts with pgsql

[BlackDex]

No it will not help to login since that is not it's purpose.
It's there to help with issues and provide an overview of users and organizations.

I have seen a lot of users facing issues when using portainer. Like settings not working, lost database etc..

Without more details on how you are running it with either screenshots of the config, or checking the admin interface, we can't help you.

As mentioned, i tested it, not using portainer though, but a clean setup new database, and i was able to create a new account and login with several clients. So, there is nothing wrong on the Vaultwarden side. But there is probably some configuration error.

[NxckyBear]

okay, it really looks like an issue on portainers end... I got it working now, tried on extension, mobile client and web and it now works... even with pgsql as backend...

Thanks for your help.

[W0lf1977]

I am facing them same issue on portainer, what was your solution?

[NxckyBear]

Set vaultwarden up via docker directly and not via portainer...

[shadowjig]

I've been running vaultwarden via Portainer since I started using vaultwarden. Portainer is not the issue. In my case, I had started up a second vaultwarden instance and had the service name in the docker compose the same name as the other instance. Since shutting the second instance down, everything is fine.