540
PSA: the bitwarden clients got an upgrade that makes them incompatible with vaultwarden (github.com)
submitted 3 days ago by to c/selfhosted@lemmy.world
57 comments fedilink hide all child comments
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] 19 points 3 days ago (1 child)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 3 days 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.

  • permalink
  • fedilink
  • source
  • parent