Currently I manage my passwords in an archaic but secure way, which is simply to synchronize a directory where I have my Keepass database between my devices, and I say archaic but secure because even if my Nextcloud server hosted on a VPS explode (where I have the database stored) I still have the databases stored locally, so I don’t lose anything.
I am currently interested in self hosting Vaultwarden although my biggest drawback is the fact that if my VPS were to fail for example I would not be able to access my database and if I lose access to the database I lose access to all my passwords. a pretty bad scenario.
So I have a question, what can I do to prevent that from happening? Apart from hosting everything on my own hardware of course, for now I prefer to use VPS for different reasons.
The Bitwarden clients all keep a cached copy of your password database, which can be viewed even if your server goes offline (you just can’t make edits) - you can even export it when that is the case.
However, if you log out of Bitwarden, it erases the local cache off that device, which will require your server to be online in order to retrieve again (or export it from a different device that is still signed in).
Awesome, thank you!
Also, you can back up your dB to encrypted json and restore it later.
AFAIK you can still make edits to the local cache when the server is offline. They just won’t sync until it regains connection.
Edit: Just tested with my phone on airplane mode and can confirm this.
Ah gotcha, most of my changes for Bitwarden occur through the browser extension, and the last time I tried to edit it while my server was offline, it would not allow me to save changes - however perhaps that was either a bug, behavior that has since changed in between then and now, or just a limitation that the browser extension(s) have that the actual apps don’t.