Release 1.37.0 · dani-garcia/vaultwarden
github.com
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...

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

  • clif@lemmy.worldEnglish
    2·
    41 minutes ago

    I’ve been leery about bitwarden client updates since the posts awhile back about the new(ish) PE/VC c suite person.

    I’m not saying those are related in any way other than the fact that I intentionally haven’t updated my clients to the latest yet and for once it worked out for me :)

    • Marthirial@lemmy.worldEnglish
      47·
      4 hours ago

      Switching to Passbolt right now. I have the feeling this is the beginning of the enshitification of Bitwarden.

    • Bazoogle@lemmy.worldEnglish
      5·
      4 hours ago

      Per the vault warden release notes:

      We strongly advice to update as soon as possible.

      With the vulnerabilities being patched these days, it seems ill asvised to disable automatic updates for something as critical as a password manager.

      • irmadlad@lemmy.worldEnglish
        2·
        4 hours ago

        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.