Caddy's automatic HTTPS reverse_proxy site block is a strong default when you want one binary to own TLS and upstream routing. I put each public hostname in its own site, reverse_proxy only the paths that should hit the app, and leave static or health endpoints explicit so a mis-scoped proxy does not swallow ACME or probe traffic.
Ops checks after reload: confirm the issued cert SANs match every site name, that http requests 301 to https on the canonical host in one hop, and that upstream connect failures show separately from timed-out reads. For WebSocket or gRPC upstreams I raise read timeouts and disable response buffering where needed; after a Caddyfile change I hit a cached static path and a dynamic path separately so a trailing-slash or Host mismatch does not look like an application bug.