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
[–] 2 points 1 month ago (1 child)

The whole client is open source, but idk if you can simply call the API with a token for a linked device or something. Pretty sure Signal doesn't want "chatbots" on their networks and it might be against ToS.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 month ago

    uhm.. yeah I need to look into that. with Telegram, I needed to register a special "telegram app token" and on top of that you still need to login with your own credentials. But I'm just using the official tdlib for that.

  • permalink
  • fedilink
  • source
  • parent