You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use Bitwarden self-hosted Unified docker normally e.g. adding passwords, setting up organization folders etc...
Sign in after a period of time and try to access data
Sign in works normally as credential information is saved, but no logins or organization data is shown in either the web or browser extension.
Expected Result
All login information and organization information would remain intact.
Actual Result
All data is gone including organization information along with billing sync data
Screenshots or Videos
No response
Additional Context
Initially saw this behavior due to how the "docker image prune" command was being ran with having the docker image down/offline. Which of course would lead to the database being wiped accidently. However, recently have seen this database wipe problem occur without having made any docker updates or performed and docker changes for many weeks.
A full VM image of the system that experienced the Bitwarden "wiped" database is available if there are certain logs that can be investigated. Had to restore production system back to an image 10 days old.
I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
Steps To Reproduce
Expected Result
All login information and organization information would remain intact.
Actual Result
All data is gone including organization information along with billing sync data
Screenshots or Videos
No response
Additional Context
Initially saw this behavior due to how the "docker image prune" command was being ran with having the docker image down/offline. Which of course would lead to the database being wiped accidently. However, recently have seen this database wipe problem occur without having made any docker updates or performed and docker changes for many weeks.
A full VM image of the system that experienced the Bitwarden "wiped" database is available if there are certain logs that can be investigated. Had to restore production system back to an image 10 days old.
Githash Version
7f8b6c0-dirty
Environment Details
-Ubuntu Server 22.04
-Docker Compose
Database Image
mariadb:10
Issue-Link
#2480
Issue Tracking Info
The text was updated successfully, but these errors were encountered: