619f2c2a7be8 bitwarden/nginx:1.38.4 '/entrypoint.sh' 3 minutes ago Up 3 minutes (healthy) 0.0.0.0:8080->8080/tcp, 80/tcp, 0.0.0.0:8443->8443/tcp bitwarden-nginxĤ847aa142d18 bitwarden/portal:1.38.4 '/entrypoint.sh' 4 minutes ago Up 3 minutes (healthy) 5000/tcp bitwarden-portalĮfac30f8bbaa bitwarden/admin:1.38.4 '/entrypoint.sh' 4 minutes ago Up 3 minutes (unhealthy) 5000/tcp bitwarden-adminĨec72401e840 bitwarden/identity:1.38.4 '/entrypoint.sh' 4 minutes ago Up 4 minutes (healthy) 5000/tcp bitwarden-identityĭ552830444fe bitwarden/icons:1.38.4 '/entrypoint.sh' 4 minutes ago Up 4 minutes (healthy) 5000/tcp bitwarden-iconsĪ15ae904ac86 bitwarden/mssql:1.38.4 '/entrypoint.sh' 4 minutes ago Restarting (1) 52 seconds ago bitwarden-mssqlĩ76bf85c735c bitwarden/sso:1.38.4 '/entrypoint.sh' 4 minutes ago Up 4 minutes (unhealthy) 5000/tcp bitwarden-ssoĤ390d4cae53c bitwarden/attachments:1.38.4 '/entrypoint.sh' 4 minutes ago Up 4 minutes (healthy) bitwarden-attachmentsĨ2dfa4c98ed8 bitwarden/web:2.17.1 '/entrypoint.sh' 4 minutes ago Up 4 minutes (healthy) bitwarden-webĮc5c20cea50c bitwarden/events:1.38.4 '/entrypoint.sh' 4 minutes ago Up 4 minutes (healthy) 5000/tcp bitwarden-eventsĭ13872fe2465 bitwarden/api:1.38.4 '/entrypoint.sh' 4 minutes ago Up 4 minutes (healthy) 5000/tcp bitwarden-apiĭ1c3b315a70a bitwarden/notifications:1.38.4 '/entrypoint. Then - just as I'm pulling my hair out - I'll go for a run or walk the dog and come back to find that everything is working again.Apparently the container is still restarting… which is confusing. I'll restart my router, the NAS, and restart the SWAG docker a few times. The log file will start saying 'Certificate Not Found, etc'. I can no longer access BW using the duckdns link. I can access BW from my internal computers, my phone, and my work computer. We built a docker setup running a container for the Bitwarden server with an Nginx proxy handling TLS connections using a self-signed certificate. I will check the SWAG log and it will say 'Server Ready' for all of my duckdn subdomains. Once Bitwarden’s container is restarted after setting the admin token, you can access the admin panel at Wrap up We finally made it.

I've properly forwarded my ports and I'm confident that I've correctly configured SWAG, BitWarden, and the necessary.

Has anybody experienced an issue where SWAG (formerly 'LetsEncrypt') will inexplicably stop resolving the secure connection when using duckdns? I've been setting up Bitwarden using SWAG as my reverse proxy.

Bitwarden docker container