posted in Selfhosted

PSA: the bitwarden clients got an upgrade that makes them incompatible with vaultwarden

If you got the automatic updates on the bitwarden clients, they will show an empty vault if you are selfhosting vaultwarden.

It seems to be an accidental bug in the bitwarden clients that are assuming that they’re talking with official servers

It’s fixed with the latest release of the vaultwarden server that was published a few minutes ago

github.com/dani-garcia/vaultwarden/releases/tag/1.37.0
Note
This update is required for support with clients with version 2026.7.0+, please update before reporting any issues with them.
Security Fixes
This release contains security fixes for the follow...GitHubRelease 1.37.0 · dani-garcia/vaultwardenNote This update is required for support with clients with version 2026.7.0+, please update before reporting any issues with them. Security Fixes This release contains security fixes for the follow...

Replying to @⁨Appoxo@lemmy.dbzer0.com⁩

That’s one of the joys of FOSS, when the dev for a popular project can’t continue; there’s often someone willing to pick up the torch and carry it forward.

I switched to this fork when the one you’re thinking of ended development.

github.com/nicholas-fedor/watchtower

Last update 3 days ago.

Automate Docker container image updates. Contribute to nicholas-fedor/watchtower development by creating an account on GitHub.GitHubGitHub - nicholas-fedor/watchtower: Automate Docker container image updatesAutomate Docker container image updates. Contribute to nicholas-fedor/watchtower development by creating an account on GitHub.