Broke Vaultwarden compatibility :( Rolling back to an old version...

Latest version breaks self-hosted Vaultwarden.

Bitwarden devs, if you're reading this: If you made it so your docker implementation of the self-hosted variant would also only take a few megabytes of diskspace and 50-100 MB of RAM, then Vaultwarden didn't even have to exist in the first place!

Right now, the official Bitwarden self-hosted option is a bloated heap of garbage.

It's not as polished as other similar password managers' extension. Even newer ones like Proton Pass is miles better in UI and performance. Maybe it's better on Chrome but I don't use trash browsers based on Chromium.

Works perfectly since years. Tip for those who have problems: Update your instance

Generally good, but they need to fix the display bug that causes functionally necessary information and buttons to be hidden off screen with no way to access.

Upgrading to vaultwarden 1.37.1 fixed the problem with extension

Self-hosted instances broke with latest update.

If it was possible i would've given this 0.25 stars as the extension is worthless.
Imported all my passwords and it doesn't even suggest any of them on any site ever.
Firefox own password manager is so much better and user friendly than BitWarden.

There’s an issue with version 2026.7.0 on self‑hosted vaults, so I rolled back to version 2026.6.1 to fix it.

Не работает с самохостингом. Почините

ubuntuのFirefoxでパスキーを利用するには必須の拡張機能。
また、ubuntu, WindowsそれぞれのFirefox, Chrome, Operaを使っている私にはどの端末のブラウザをつかってもパスキーやパスワードが同期されていることが素晴らしい。

It used to work nicely but in the last month, I have to reenter my 4 bitwarden accounts at least once a week because it loose them. One of them isn't even self hosted...

Self-hosting require updating the server version to 1.37.1; otherwise, they will not work.

Latest update broke usability in combination with self-hosted solutions

For a few days, my vaultwarden wasn't loading. This was annoying. We updated our vaultwarden, did a full log-off and then it started working again. still annyoing.

Same here. Not workling with self-hosted vaultwarden. The solution ist simple: update your server.