# Bitwarden 2026.3.0 MSSQL Container Problem

**URL:** <https://community.bitwarden.com/t/bitwarden-2026-3-0-mssql-container-problem/95152>\
**Category:** Password Manager\
**Tags:** os:linux, server:selfhost, app:all\
**Created:** [March 21, 2026, 4:41pm UTC](https://community.bitwarden.com/t/bitwarden-2026-3-0-mssql-container-problem/95152 "2026-03-21T16:41:17Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![bglf83](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/bglf83/32/45908_2.png) [@bglf83](https://community.bitwarden.com/u/bglf83)\
**Post date:** [March 22, 2026, 5:34pm UTC](https://community.bitwarden.com/t/bitwarden-2026-3-0-mssql-container-problem/95152/10 "2026-03-22T17:34:03Z")

</div>

I am also hosting on Synology (DS1621+) running DSM 7.3.2.

I did some research before rolling back, and it is risky rolling back databases to older versions (stop bitwarden before doing this). I restored my files to the previous day to ensure my stuff would be ok before doing it.

Inside bitwarden.sh line 67-70, change the COREVERSION and WEBVERSION to the 2026.2.1 which is the previous version.

> # Please do not create pull requests modifying the version numbers.
> 
> COREVERSION=“2026.2.1”
> 
> WEBVERSION=“2026.2.1”
> 
> KEYCONNECTORVERSION=“2025.11.0”

After that, update docker-compose.yml all images to version 2026.2.1.

I then did a bitwarden.sh stop, then bitwarden.sh rebuild and then a bitwarden.sh start.

[https://bitwarden.com/help/install-on-premise-linux/#script-commands-reference](https://bitwarden.com/help/install-on-premise-linux/#script-commands-reference)

@Nail1684 the issue does appear to be the same one you linked too on GitHub.

---

_[View the full topic](https://community.bitwarden.com/t/bitwarden-2026-3-0-mssql-container-problem/95152)._
