Upgrading from Option B to Option A and Managing the Caddy Container

DNS Setup (Azure)

Upgrading from Option B to Option A

Once a domain is available, switch without rebuilding the container:

cat > ~/caddy/Caddyfile <<'EOF'
hivel.yourcompany.com {
    reverse_proxy localhost:3000
}
EOF
 
docker restart caddy

Expected result: Caddy detects the change and automatically requests a Let's Encrypt certificate on restart.

Managing the Caddy Container

# View logs
docker logs -f caddy
 
# Restart (e.g. after editing the Caddyfile)
docker restart caddy
 
# Stop
docker stop caddy
 
# Remove entirely (application remains reachable on :3000 directly)
docker rm -f caddy

Certificates are stored in the caddy_data Docker volume and persist across container restarts and upgrades, so renewals happen automatically without re-issuing from scratch.

Next: Troubleshooting.

Option B - Self-Signed

Troubleshooting