Nuking docker-compose data/ directory does not completely reset vaultwarden? #6436
Unanswered
WillNilges
asked this question in
Q&A
Replies: 1 comment
-
|
Weird, it seems like my browser might have been caching. This is a bit concerning, because it appeared to allow me to log in. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I've got a vaultwarden instance configured with an almost-bog-standard docker-compose as in the README.
I wanted to test my backups, so I added some passwords, spun down my vaultwarden, erased my data directory (
sudo rm -rf /home/wilnil/app_storage/vaultwarden/) and re-deployed my instance. I was shocked to find that it was asking for my master password! I entered the master password, and it let me in, but my passwords are gone.This is concerning, because it seems to imply that my passwords are stored in the
data/directory, which is great, that means they are backed up, but then there's configuration... 👋🏻 elsewhere 👋🏻 that I don't know about, and is almost certainly not backed up.Does anyone have any idea what is going on?
Beta Was this translation helpful? Give feedback.
All reactions