mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-11 09:13:02 +03:00
Vault empty; No longer Part of Organisations #2053
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 @davidh2k on GitHub.
I have an issue, when I log into the webinterface (or any new remote client) I have an empty Vault, it even states that I'm no longer part of any of my two organisations.
However, if i look at the admin panel, it still shows my belonging to the two organisations:
I already did a backup of my still synched desktop client that had the passwords still. Any ideas how my vault can be empty? Could that hapenned on a container update?
@jamestutton commented on GitHub:
Can confirm I am experiencing a similar issue. In my case I created a new org owner and the downgraded the original owner to a "User" permissons didnt seem to update correctly so remove the user and readded and now they cant see the org at all. Will see if i can replicate in a test env and update.
@davidh2k commented on GitHub:
For Sanity checking I just added one dummy password and both restarted and --force-recreate'd the container via docker-compose - dummy password still there.
@davidh2k commented on GitHub:
Maybe this is in any way related to https://github.com/dani-garcia/bitwarden_rs/issues/494 ?
@davidh2k commented on GitHub:
I just kinda solved it by pulling the current image and switching from version:
to:
Log now shows:
And Webinterface shows all passwords and organisations again. So in fact maybe really related to #494 ?
Solved for the moment, but worth investigating more?
@mprasil commented on GitHub:
The previous version you used was quite old. It's still strange that it was failing this way, but not sure how we can troubleshoot further unless you have some way to reproduce it again.
If it ever happens again, one thing worth trying is to log out the user, force-reload the interface (ctrl-shift-r) and log in again.
@jamestutton commented on GitHub:
Sorry not sure where this issue was coming from. Not able to recreate with current version. And when pointed the latest docker image at my original data the issue went away. So can only assume what ever was the cause has been fixed.
@mprasil commented on GitHub:
Closing this now, but feel free to reopen if you can find some way to reproduce the problem.