I have an offline install of Bitwarden which always seems to have the docker containers stay “unhealthy” after a while.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
56ccc1c084b5 bitwarden/nginx:2023.9.0 "/entrypoint.sh" 5 hours ago Up 5 hours (unhealthy) 80/tcp, 0.0.0.0:80->8080/tcp, 0.0.0.0:443->8443/tcp bitwarden-nginx
8e3c4c90fb56 bitwarden/admin:2023.9.0 "/entrypoint.sh" 5 hours ago Up 5 hours (unhealthy) 5000/tcp bitwarden-admin
457ce8fefdb4 bitwarden/icons:2023.9.0 "/entrypoint.sh" 5 hours ago Up 5 hours (unhealthy) 5000/tcp bitwarden-icons
be7e0ed9ed2a bitwarden/attachments:2023.9.0 "/entrypoint.sh" 5 hours ago Up 5 hours (unhealthy) bitwarden-attachments
9c360473360a bitwarden/sso:2023.9.0 "/entrypoint.sh" 5 hours ago Up 5 hours (unhealthy) 5000/tcp bitwarden-sso
360881caef19 bitwarden/notifications:2023.9.0 "/entrypoint.sh" 5 hours ago Up 5 hours (unhealthy) 5000/tcp bitwarden-notifications
ed48634a7d60 bitwarden/web:2023.9.1 "/entrypoint.sh" 5 hours ago Up 5 hours (unhealthy) bitwarden-web
08ec1c8172b8 bitwarden/events:2023.9.0 "/entrypoint.sh" 5 hours ago Up 5 hours (unhealthy) 5000/tcp bitwarden-events
8ff117ebad15 bitwarden/identity:2023.9.0 "/entrypoint.sh" 5 hours ago Up 5 hours (unhealthy) 5000/tcp bitwarden-identity
356815a9e20e bitwarden/mssql:2023.9.0 "/entrypoint.sh" 5 hours ago Up 5 hours (healthy) bitwarden-mssql
4b1ac837ab77 bitwarden/api:2023.9.0 "/entrypoint.sh" 5 hours ago Up 5 hours (unhealthy) 5000/tcp bitwarden-api
This install is self-hosted and does not have internet access, so I’m wondering if this unhealthy state is just a result of that and not something that really needs investigating.
In my instance, I have nginx running as a reverse proxy providing SSL termination with a certificate. I also appear to have an issue where after a while, the Bitwarden web interface no longer works and when I try to access it, I just get a gateway timeout suggesting a problem with the Bitwarden web front end.
I don’t know if these two things (unhealthy status and bitwarden no longer working after a few days) are related.
This happens on my old instance running 2023.4 and also once I upgraded it to 2023.9 which is what it’s currently on.