▲ 551 ▼ PSA: the bitwarden clients got an upgrade that makes them incompatible with vaultwarden (github.com) submitted 1 month ago by Wispy2891@lemmy.world 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
[–] ramble81@lemmy.zip 3 points 1 month ago (1 child) “Accidental” — you are far more trusting than I permalink fedilink source hideshow 1 child comment replies: [–] Lem453@lemmy.ca 14 points 1 month ago If you check the github discussion from the devs that patched the issue it doesn't seem intentional to me (not an expert). That being said I assumed the same thing. My browser auto updated the extension at a very inopportune time and from some reason KDE connect from my phone to computer which is usually very reliable also wouldn't connect. Was quite annoying until I realized I can just log into the vaultwarden website directly. I don't think I've done that in years permalink fedilink source parent
[–] Lem453@lemmy.ca 14 points 1 month ago If you check the github discussion from the devs that patched the issue it doesn't seem intentional to me (not an expert). That being said I assumed the same thing. My browser auto updated the extension at a very inopportune time and from some reason KDE connect from my phone to computer which is usually very reliable also wouldn't connect. Was quite annoying until I realized I can just log into the vaultwarden website directly. I don't think I've done that in years permalink fedilink source parent