[GH-ISSUE #1216] Wrong Master password unless I logout and re-login #859

New issue

Closed

opened 2026-03-03 02:04:05 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @mind-overflow on GitHub (Nov 3, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1216

As already mentioned in the official Bitwarden forum, the new Bitwarden version inclused fundamental API changes that break login in extensions, desktop apps, etc...
Fortunately, logging in still works if you click "Disconnect" before attempting to enter the password.
These API changes need to be implemented directly into the server.
Related thread: here.

Originally created by @mind-overflow on GitHub (Nov 3, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1216 As already mentioned in the official Bitwarden forum, the new Bitwarden version inclused fundamental API changes that break login in extensions, desktop apps, etc... Fortunately, logging in still works if you click "Disconnect" before attempting to enter the password. These API changes need to be implemented directly into the server. Related thread: [here](https://community.bitwarden.com/t/self-hosted-master-password-only-works-after-logout/15231).

kerem closed this issue

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

kerem commented

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

Author

Owner

@BlackDex commented on GitHub (Nov 3, 2020):

This has been fixed over a month ago in #1158 .
Please update your bitwarden_rs to the latest version available, see: #1180

@BlackDex commented on GitHub (Nov 3, 2020): This has been fixed over a month ago in #1158 . Please update your bitwarden_rs to the latest version available, see: #1180

kerem commented

2026-03-03 02:04:07 +03:00

Author

Owner

@mind-overflow commented on GitHub (Nov 3, 2020):

Understood. I have updated it to 2.16.1 a few hours ago and was still getting the error, so that's why I opened the issue. I guess it was because of caching. Sorry for the trouble!

@mind-overflow commented on GitHub (Nov 3, 2020): Understood. I have updated it to 2.16.1 a few hours ago and was still getting the error, so that's why I opened the issue. I guess it was because of caching. Sorry for the trouble!