I started having issues opening a password protected entry across extensions/desktop/mobile. Went to https://www.reddit.com/r/Bitwarden/ and there are a bunch of posts in the past few days talking about similar issues
How do you guys keep your Bitwarden backed up? This reminded me to properly set that up. For now, I just exported the file and left it encrypted on a separate drive.
I'm not sure if this issue was with Bitwarden's own hosted version, but I've noticed on multiple occasions that it gets weird and it's always a version mismatch issue. I got this master password prompt because my browser extensions auto update, my server does not. I updated VaultWarden on my server and that resolved the issue.
They really need to add version warnings in the clients. e.g. "your server is in X.X.X and is out of date for use with this app and may not work properly, continue?".
As for backups - I use Docker and backup my entire VaultWarden instance daily. If something goes wrong I can restore an older backup and try again.
Every week i backup my vault and totp seeds to an encrypted cloud storage.
I have a difficult time trustimg cloud storage providers. How do you do it?
I use cryptomator to encrypt what im uploading ahead of time.
Its one of the rare times where Google pays off. G drive is relatively secure and cryptomator makes it decently private.
It's definetly a good idea to export a backup just in case. I have a local desktop backup with KeePassXC and every couple of months or so I export the file, encrypt it and upload a copy on proton drive and another on a personal external drive
I switched from Bitwarden to using Pass for reasons like this.
How do you guys keep your Bitwarden backed up?
I go do a manual export to CSV every few weeks, then store that in a cryptomator vault I use for important stuff.
Every browser extension and mobile app keeps a copy. Between 2 PC's, 1 Macbook, 1 iPad and 1 iPhone I think I will survive a server crash
Not really a server crash but a bug that stops you from unlocking the vault. I guess going to an earlier version of it might help, but that would take time if you needed something quickly
Sounds like a "RAID is not a backup" situation.