Hello
Last week I updated both my self-hosted Bitwarden instance and the MariaDB instance on my Docker setup on Synology which I had installed via Portainer Stack following these instructions:
The Docker images involved are as follows:
• bitwarden/self-host:beta
• mariadb:11.4-noble
Since the update, after entering my password, I receive an error message stating that an unexpected error has occurred. I can no longer log in, and in particular, cannot back up the organization’s data. Additionally, my attempt to access the admin page has been failing since then (Bad Gateway).
The bitwarden container logs show the following:
2024-10-31 08:38:37,103 INFO spawned: ‘admin’ with pid 1011
2024-10-31 08:38:52,124 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2024-10-31 08:39:05,162 WARN exited: admin (terminated by SIGABRT (core dumped); not expected)
2024-10-31 08:39:06,164 INFO spawned: ‘admin’ with pid 1043
2024-10-31 08:39:21,187 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
…
The mariadb container logs show the following:
2024-10-31 9:25:35 5 [Warning] Aborted connection 5 to db: ‘bitwarden_vault’ user: ‘bitwardenuser’ host: ‘’ (Got an error reading communication packets)
2024-10-31 9:26:04 9 [Warning] Aborted connection 9 to db: ‘bitwarden_vault’ user: ‘bitwardenuser’ host: ‘’ (Got an error reading communication packets)
…
In the meantime, I have deleted the containers, backed up the existing Docker folders to a different location, and then deleted the docker folders to perform a fresh setup. However, even after such a clean reinstallation(s), the same errors persist. I am able to register, but I cannot log in afterward and can’t access the admin page.
I updated both containers several times in the past without any issues and there was nothing I did in another way now.
The official support didn‘ react at first and told me the following on Monday:
„May i ask that you try this;
This issue could be happening because of permissions when the Docker Synology application is enabled on a volume other than the default volume created in Synology. (for example, /volume6) when the Docker Synology app is installed, two directories are created: /volume6/docker and /volume6/@docker.
However, the permissions are different between the two; the former directory gets write access for the docker_bitwarden user, while the latter does not. Changing the permissions on the latter:
chown -R docker_bitwarden @docker/“
Unfortunately this didn’t help. I immediately informed the support and since then – again – they do not react.
Can anyone please help since Bitwarden, including the paid license, is currently of no use to me?
Thank you…
