mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
User Vaults Lost #322
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @spaerk on GitHub (Jun 15, 2019).
So in the last few days, the Bitwarden android app has been updated, and it immediately conflicted with my Bitwarden host - It just kept giving an error about not being able to connect to the server. I ended up uninstalling the newest version and installing the version from February (1.22) and that seemed to connect fine, and let me access my vault.
Today, my mom mentions that she can't log into her vault, and I assume it was the same issue. So I did the same version downgrade, before we get hard stopped at her master password. I assume she forgot it, which sucks, but we can recover her few passwords. So I go to /#/recover-delete and enter her email, but get an error. So I try logging into my vault. I know my password. Username/Password not recognized. Enabled, and then connected to the admin panel and find there are no vaults. At all. After 2 months of using Bitwarden, my whole vault is just gone. I even tested by creating a new user with the email I've been using the whole time, and now I see a registered user in the Admin panel.
I'm very likely to have just screwed up - bad. I assume I rebooted the container badly, or did something. I'm hoping I didn't wipe my vault, I just misplaced it or something. I don't really know where to start looking to see if I even still have the old Vault.
@dani-garcia commented on GitHub (Jun 15, 2019):
The recover delete endoint isn't implemented so that explains the error (I don't even know how to get there without changing the URL by hand). I don't think that could be the cause of the error, because it's just gonna return a 404 and do nothing more.
Just to get a clearer picture, you:
If nothing else happened, I have no idea what could be the cause of the problems, the database should be able to resist a reboot without problems.
I'd try to open the db.sqlite3 file with something like DB Browser and check if there are contents in the Users table and the Ciphers table.
I'd also try to check if you have any other client logged in, make sure the device is offline and try to access your vault from there, you'll have to export the passwords by hand but it's something I guess.
I'd also check if you have any docker volumes created, maybe you used a volume before but when rebooting to enable the admin page you switched to mounting the local file system directly?
@spaerk commented on GitHub (Jun 15, 2019):
DB Browser gives me an Invalid File Format error when opening the db.sqlite3 file. Which doesn't give me much hope.
After the initial install, I started mostly using Kitematic to check on/reboot/manage the container, and used it to enable the admin panel, would this have any relevance?
@spaerk commented on GitHub (Jun 15, 2019):
Solved it! You nailed it with the Volume idea. I somehow changed it in Kitematic, and didn't even realize it. Set it back to /bw-data/ and we're good to go!
Both our vaults now show from the admin panel, any all my devices log in and show my vault. Now I can remove her vault and start a fresh user with a better Master password.