Self-Hosted Install Issue

Ask the Bitwarden Community
#1

Hello -

I performed a self-hosted install, and everything went fine until I tried to create a new account on the BitWarden sign-in page. After a little digging, it looks like the bitwarden-mssql container is unhealthy.

Then after digging into the mssql logs, it appears the account “sa” is unable to log into the mssql server. I check the config files in /env and the password in the msssql.override.env and global.override.env match.

Any ideas?

5be6f1e8e378 bitwarden/mssql:1.32.0 “/entrypoint.sh” 8 minutes ago Up 8 minutes (unhealthy) 1433/tcp bitwarden-mssql

2020-03-05 06:34:28.45 spid21s Service Broker manager has started.
2020-03-05 06:34:28.52 spid6s Recovery is complete. This is an informational message only. No user action is required.
2020-03-05 06:34:38.43 Logon Error: 18456, Severity: 14, State: 8.
2020-03-05 06:34:38.43 Logon Login failed for user ‘sa’. Reason: Password did not match that for the login provided. [CLIENT: 172.18.0.7]
2020-03-05 06:34:44.54 Logon Error: 18456, Severity: 14, State: 8.
2020-03-05 06:34:44.54 Logon Login failed for user ‘sa’. Reason: Password did not match that for the login provided. [CLIENT: 172.18.0.10]
2020-03-05 06:35:04.60 Logon Error: 18456, Severity: 14, State: 8.
2020-03-05 06:35:04.60 Logon Login failed for user ‘sa’. Reason: Password did not match that for the login provided. [CLIENT: 172.18.0.10]
2020-03-05 06:35:08.77 Logon Error: 18456, Severity: 14, State: 8.
2020-03-05 06:35:08.77 Logon Login failed for user ‘sa’. Reason: Password did not match that for the login provided. [CLIENT: 172.18.0.7]
2020-03-05 06:35:24.68 Logon Error: 18456, Severity: 14, State: 8.
2020-03-05 06:35:24.68 Logon Login failed for user ‘sa’. Reason: Password did not match that for the login provided. [CLIENT: 172.18.0.10]

#3

I had this same issue. If you installed bitwarden previously and did not remove the persistent volume that the bitwarden installer added the first time then it tries to connect to it but your password is likely now different. The solution for me was to remove the persistent volume then when I started it up created a new one with the new password and everything worked.

#4

@Rydestudio what specifically do you mean by “remove the persistent volume”?

I’ve installed and re-installed multiple times, and everything about the configs looks like the passwords should line up correctly.

#5

@chad.mercer I was using the docker desktop application and when I used the cleanup function to remove the images. What I found is that this does not remove the volume that it creates to store the database. I am also using portainer and this is how I found that when I went to volumes within portainer that it informed me I had unused volumes. I removed the unused volumes then when I installed bitwarden again it worked.

#6

Thanks for the clarification. Turns out I was trying to run Bitwarden on a Linode that couldn’t handle it.

docker logs bitwarden-mssql

showed that MSSQL can’t run in less than 2GB of RAM. Upgraded to a more robust Linode “machine” and it came right up.

Amazing.