Admin, sso and icons container unhealthy

Ask the Bitwarden Community
#1

Dear community,

We have a problem with a on premise installation on a synology DS. From January 31th to February 1st something happened with our setup and bitwarden stopped working. The container “bitwarden-admin”, “bitwarden-sso” and “bitwarden-icons” are in status unhealthy:

[email protected]:/volume1/Docker$ sudo docker ps
Password:
CONTAINER ID        IMAGE                            COMMAND             CREATED             STATUS                      PORTS                                            NAMES
85e04c13702b        bitwarden/nginx:1.39.4           "/entrypoint.sh"    12 minutes ago      Up 11 minutes (healthy)     80/tcp, 8443/tcp, 0.0.0.0:8124->8080/tcp         bitwarden-nginx
af352fbb504a        bitwarden/portal:1.39.4          "/entrypoint.sh"    12 minutes ago      Up 12 minutes (healthy)     5000/tcp                                         bitwarden-portal
be6ca27e15b1        bitwarden/admin:1.39.4           "/entrypoint.sh"    12 minutes ago      Up 12 minutes (unhealthy)   5000/tcp                                         bitwarden-admin
9c3325092139        bitwarden/mssql:1.39.4           "/entrypoint.sh"    13 minutes ago      Up 12 minutes (healthy)                                                      bitwarden-mssql
5e50e5ce2bc2        bitwarden/sso:1.39.4             "/entrypoint.sh"    13 minutes ago      Up 12 minutes (unhealthy)   5000/tcp                                         bitwarden-sso
9aa13cd55ef8        bitwarden/web:2.18.1             "/entrypoint.sh"    13 minutes ago      Up 12 minutes (healthy)                                                      bitwarden-web
ae38eb1ea542        bitwarden/attachments:1.39.4     "/entrypoint.sh"    13 minutes ago      Up 12 minutes (healthy)                                                      bitwarden-attachments
9aabcc2d8e8e        bitwarden/identity:1.39.4        "/entrypoint.sh"    13 minutes ago      Up 12 minutes (healthy)     5000/tcp                                         bitwarden-identity
fe0b36bfb5ab        bitwarden/events:1.39.4          "/entrypoint.sh"    13 minutes ago      Up 12 minutes (healthy)     5000/tcp                                         bitwarden-events
a5f0971f65d2        bitwarden/notifications:1.39.4   "/entrypoint.sh"    13 minutes ago      Up 12 minutes (healthy)     5000/tcp                                         bitwarden-notifications
1f23a8663bce        bitwarden/api:1.39.4             "/entrypoint.sh"    13 minutes ago      Up 12 minutes (healthy)     5000/tcp                                         bitwarden-api
84ebcb1e523a        bitwarden/icons:1.39.4           "/entrypoint.sh"    13 minutes ago      Up 12 minutes (unhealthy)   5000/tcp                                         bitwarden-icons

Admin-Log shows the following error on and on:

System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server)

Database (mssql) looks fine / tried restoring a backup from January 30th and restarting, but still the same.

Is there any way to recreate/rebuild the installation with existing / without loosing data?

Best regards!

#2

Same. Fresh Install on Ubuntu 20.04.2 LTS and I get the same. I changed no perimeters aside from SMTP settings.

#3

Same here, any development because is becoming frustrating.

[[email protected] bitwarden]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8a17b934a7fc bitwarden/admin:1.39.4 “/entrypoint.sh” 6 minutes ago Up 6 minutes (unhealthy) 5000/tcp bitwarden-admin
c68adcce0c8a bitwarden/sso:1.39.4 “/entrypoint.sh” 6 minutes ago Up 6 minutes (unhealthy) 5000/tcp bitwarden-sso

#4

For me moving to another synology with the bwdata-directory worked to be able to access the container again. Did an export and moved to bitwarden_rs, which is way easier to handle.

#5

Similar issue for me… See here:

#6

Similar issue for me… See here: