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 @⁨Bazoogle@lemmy.world⁩

it seems ill asvised to disable automatic updates

I use the WatchTower fork for now, but I use it with the run once flag:

 volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    command: --run-once --cleanup

So, when an update is available, I’ll delay updating until I am rather comfortable that all the early adopters have worked out all the bugs for me. LOL Thanks guys! You’re an invaluable service.