I have a Bitwarden docker running, but the container is somehow not reachable. If I try to access https://my.domain.tld:9443/ Chrome shows “ERR_CONNECTION_CLOSED”.
The containers are up and running and the ports seem to be correct for me.
# docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b454ebeb3af5 bitwarden/icons:1.25.0 "/entrypoint.sh" 27 hours ago Up 27 hours 5000/tcp bitwarden-icons
127d889c932a bitwarden/nginx:1.25.0 "/entrypoint.sh" 27 hours ago Up 27 hours 80/tcp, 0.0.0.0:9443->8443/tcp bitwarden-nginx
a8cc679d2907 bitwarden/attachments:1.25.0 "/entrypoint.sh" 27 hours ago Up 27 hours 5000/tcp bitwarden-attachments
b06149bf8406 bitwarden/api:1.25.0 "/entrypoint.sh" 27 hours ago Up 27 hours 5000/tcp bitwarden-api
01aa05e22087 bitwarden/identity:1.25.0 "/entrypoint.sh" 27 hours ago Up 27 hours 5000/tcp bitwarden-identity
8c55143dcf32 bitwarden/mssql:1.25.0 "/entrypoint.sh" 27 hours ago Up 27 hours 1433/tcp bitwarden-mssql
c6bd7e9fc9f5 bitwarden/notifications:1.25.0 "/entrypoint.sh" 27 hours ago Up 27 hours 5000/tcp bitwarden-notifications
3c78402b8a06 bitwarden/web:2.4.0 "/entrypoint.sh" 27 hours ago Up 27 hours 5000/tcp bitwarden-web
8f340cb4ff7e bitwarden/admin:1.25.0 "/entrypoint.sh" 27 hours ago Up 27 hours 5000/tcp bitwarden-admin
The nginx error log within the container shows nothing and the access log also doesn’t show any accesses in the access.log, so the request doesn’t seem to go through, but I think it’s not a firewall issue.
# ufw status
Status: active
To Action From
-- ------ ----
[...]
9443/tcp ALLOW Anywhere
9443/tcp (v6) ALLOW Anywhere (v6)
I don’t know what the issue could be, so hopefully someone can give me a good idea how to solve this.