-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
self-hosted server containers update to 2024.2.2 hoses vaults #3849
Comments
Hi there, I attempted to reproduce your issue and was unable to do so. We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/). You can include a link to this issue in the message content. Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/). The issue here will be closed. Thanks! |
I reproduce dit for a total of 4 times. I recovered by downgrading to 2024.1.2. Restored db from mssql backup. Installed 2024.2.2 with bitwarden.sh update and it happened every time. Maybe computers are not so deterministic as we think. |
For future googlers: the issue I have found is that, no matter how I install 2023.2.2 - there is always an error indicting that there are keys missing from the keyring
|
Steps To Reproduce
I run a self-hosted server from containers.
Update via
bitwarden.sh update
to last release
connect via web or browser app
User vaults are empty.
Expected Result
User vaults should be available after update
Actual Result
it seems that something is happening with asp.net
I tried the update several times - I have often seen this error
The key {3943d9ce-1716-4c67-bfb4-08efe5a54371} was not found in the key ring. For more information go to https://aka.ms/aspnet/dataprotectionwarning
for future internet navigators, there is a path to recovery by downgrading all containers to 2024.1.2
Screenshots or Videos
No response
Additional Context
No response
Build Version
2024.2.2
Environment
Self-Hosted
Environment Details
Issue Tracking Info
The text was updated successfully, but these errors were encountered: