this post was submitted on 10 Oct 2026
454 points (98.7% liked)
Technology
88823 readers
3420 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've been self-hosting vaultwarden for a year and this has literally never happened to me.
it happens to me once or twice a year, and to people for whom I have installed bitwarden too. official clients, bitwarden.com server.
Maybe that's a bitwarden issue, I guess. One more point for selfhosting. Also, even if that were to happen to you, you most likely have it installed in more than one device. The chances of all sessions logging out at the same time would be extremely low.
not all devices, but multiple of them did log out roughly the same time. so, don't rely on storing the 2FA authenticator app's password in it.
Or just use and maintain Vaultwarden properly. All you need to do is set up watchtower along with vaultarden and you'll always be up to date. I've never had this problem so yes, I will continue to store my credentials there :)
if the official, commercial servers can't avoid this, what more could I do? I can't even provide redundancy.
on top of that, we run vaultwarden at work. both times this year compatibility was fucked up by a client update, me and my colleagues had to completely reset the client because it bugged away so hard.
sounds like a horrible idea with any software. patch versions could be fine, perhaps, but vaultwarden does not follow semver.
You can set a custom delay for automatic updates in watchtower. Also, what does "compatibility was fucked up by a client update" mean? Compatibility between Vaultwarden and the oficial bitwarden client? I've been running it for more than a year and did not have any problems whatsoever. Sounds like the reset worked for you guys, but the issue wasn't that "compatibility was fucked up". Even if something like that were to happen, why not switch to another client temporarily? Nuking the whole thing sounds like a lazy fix.
yes, that's what I meant. multiple people noted in the respective vaultwarden github issue.
yes. it was that. look up the vaultwarden issues, they were very popular.
well, the web client served by vaultwarden continued to work
there were no other options with the clients. simple as that. if you can't even go to the settings what would you do? what would you do if you can, but the sync button prints failure every single time, even after updating vaultwarden to a fixed version? lazy fix my ass.
They couldn't downgrade the clients? Sounds like that was the easiest option. You can also temporarily use something Keyguard, or why not, permanently given the latest news from Bitwarden.
Since providing sources was too hard, apparently. I think you're referring to this issue from August for example? Issue was reported on August 20th and was fixed by September 7th. Kinda sounds like you wouldn't have problems if you restricted updates for your users. Delay updates by a few weeks (or why not, a month) unless they're absolutely necessary and you're golden.
Like I said, there are options. Maybe instead of blaming Vaultwarden, you could learn from your own mistakes.
downgrading? without resetting them? how do you do that? often when complex software updates, they update their database structure, and you can't just go back without reset because the older version does not know what to do with those new columns or that renamed one. I don't know about browser addon stores but I do know android does not allow downgrading apps without uninstalling them first, for exactly this reason.
we updated vaultwarden, but after that the clients were still broken because they have already stored the state they couldn't process.
yes we were using the webapp for a short while, but that always locks to password, can't do autocomplete, and you need to always have yet another tab or browser window around for it.
"my users" don't have corporate controlled devices. even our own devices we mostly manage how we want, this is not big tech or fortune 500 top high security with mandated keystroke logging spyware. it does not matter even, as vaultwarden is not primarily for businesses. I could not prevent it for anyone for whom I'm hosting vaultwarden as a favor, even. are you suggesting to install remote monitoring and lockdown software for them all, to fix issues made by bitwarden? that would be insane.
where did I blame vaultwarden? its bitwarden official clients are whats so unstable.