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
Issue:
Following a recent upgrade to Proxmox 8.2.2, the MySQL Docker container for our self-hosted Bitwarden server has started crashing approximately every minute. This issue has rendered new logins impossible, although devices that were previously logged in can still access the server. The problem seems to have started immediately after the Proxmox update.
Steps to Reproduce:
Upgrade to Proxmox 8.2.2.
Attempt to login to the Bitwarden server.
Observe that the MySQL container crashes and restarts every minute, preventing new logins.
Additional Context:
A suggested workaround found on the Bitwarden community forum involves downgrading the kernel (see post: https://community.bitwarden.com/t/mssql-container-no-longer-accessible/62366). However, this is not a viable long-term solution. This issue is urgent as it impacts our ability to access essential security services for work.
We need urgent assistance to resolve this as it's impacting our ability to operate securely. Any help would be greatly appreciated!
Docker Version: Docker version 26.0.0, build 2ae903e
Issue Tracking Info
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
Issue:
Following a recent upgrade to Proxmox 8.2.2, the MySQL Docker container for our self-hosted Bitwarden server has started crashing approximately every minute. This issue has rendered new logins impossible, although devices that were previously logged in can still access the server. The problem seems to have started immediately after the Proxmox update.
Steps to Reproduce:
Additional Context:
A suggested workaround found on the Bitwarden community forum involves downgrading the kernel (see post: https://community.bitwarden.com/t/mssql-container-no-longer-accessible/62366). However, this is not a viable long-term solution. This issue is urgent as it impacts our ability to access essential security services for work.
We need urgent assistance to resolve this as it's impacting our ability to operate securely. Any help would be greatly appreciated!
Logs
Expected Result
Expected Behavior:
The MySQL container should remain stable and allow for continuous operation and authentication of users.
Actual Result
Steps to Reproduce:
Screenshots or Videos
No response
Additional Context
Running LXE Container so the Hosts kernel is used.
Rebuilding bitwarden did not help.
Build Version
bitwarden.sh version 2023.12.0
Environment
Self-Hosted
Environment Details
Environment:
Issue Tracking Info
The text was updated successfully, but these errors were encountered: