mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #2634] "No data available in table" after update docker image on unraid #1332
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1332
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @roukmoute on GitHub (Jul 20, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2634
After an update of vaultwarden docker image (2022.6.2) on my unraid machine, I can't connect anymore.
After connecting me on
/admin, I see this onUserstab:Where is stored my passwords with SQLite?
I've checked this:
I'm really worried, because if a simple update broke all my passwords, I am struggling because I have no copy of theses passwords.
@BlackDex commented on GitHub (Jul 20, 2022):
First, if you have any client still having the data visible, try to export that data as a json to preserve what you have right now.
@BlackDex commented on GitHub (Jul 20, 2022):
Second. An update/upgrade of the container doesn't delete any data. There could be some database migrations, but that is about it.
I do see two sqlite3 file of which one seems to be a backup, and the other seems to be the current version, since it also has the
-shmand-waltemp files there.Those should contain all the data, and just in case, i would copy those files to an other safe place just in case.
Besides that, i would double check your docker config. It could be that unraid (which i have never used my self) created a new volume, which in turn generates an empty environment and no passwords/accounts.
Please check the volume location and if that matches.