551
PSA: the bitwarden clients got an upgrade that makes them incompatible with vaultwarden (github.com)
submitted 1 month ago by to c/selfhosted@lemmy.world
58 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 1 month ago (3 children)

I love podman quadlets, I didn't do anything and it updated itself 😁

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 6 points 1 month ago (2 children)

    I run watchtower on a cron schedule. It had already fired for today, so it wouldn't have run again until tomorrow. I could have waited, but manual is just as easy.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 1 month ago (1 child)

    Be aware that watchtowerr is not updated anymore and due to the nature of having access to the socket is a security risk.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •