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
Lmao there it is
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 :)
“Accidental” — you are far more trusting than I
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
Thanks, probably saved me a lot of headache on my laptop browsers. Fortunately, I don’t use the official Bitwarden client on android partly because this seems to keep happening.
Thank you for the PSA good friend!
Do not update any bitwarden client until you can update vaultwarden
If anyone’s Firefox auto updated like mine you can uninstall the extension, go to the Bitwarden extension page on the Firefox website and manually install the old version. Only needed if you can’t update vaultwarden right away.
Switching to Passbolt right now. I have the feeling this is the beginning of the enshitification of Bitwarden.
@Marthirial @Wispy2891 They are quickly moving towards enshitification, but this was likely just a planned patch and not intentional shot across the bow. As someone mentioned, they aren’t required to check 3rd party software. But it does suck when it happens.
Bitwarden has been in decline for a while. This is definitely not the first sign.
Such bugs have already appeared in the past. It’s only logical that this happens from time to time, as the creators of bitwarden don’t test the compatobility with 3rd party servers.
What is important is that they’re not deliberately blocking vaultwarden.
The packaged Debian version did not get updated yet.
Tale as old as time.
I do love docker + a front end like dockge.
Saw this post, switched to my browser, clicked three buttons; vaultwarden is now updated. Didn’t even move my lazy ass off the couch. (I’m on my phone)
Thanks for the PSA! :)
I can recommend Arcane as a front end. I switched over all my services this last week from multiple dockges to a single arcane (+agents). It’s looking pretty sweet now. Cleans up a lot of bookmarks too 😆
I love podman quadlets, I didn’t do anything and it updated itself 😁
Wow! Thanks for the PSA!
Ps. I notice your msn avatar. I’m busy with https://retromessenger.com. Coming soon for free!
Would love this to work with Signal and Matrix!
Was wondering why it suddenly was stuck loading, thanks!
Yeah I updated bitearden yesterday and my vault would not load any items. Glad this bug is already fixed!
Thank you for this. I thought I was going insane. Time to turn auto updates off
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.
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 --cleanupSo, 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.
Removed by mod
