How do you handle SSL renewals across multiple self-hosted apps?
retained text
Managing SSL certificates across a bunch of self-hosted services is the one part of self-hosting that still catches me off guard. You set up certbot, cron the renewal, and most months it's fine. Then a custom domain expires, a DNS record changes, a container restarts at the wrong time, and suddenly a client site is showing a cert error at 2 AM. I've been through enough of those fire drills to know the "set and forget" approach works until it doesn't. The moment you add a custom domain or move a service, the renewal chain breaks silently and you find out from a user, not from a monitoring alert. For those of you running several apps on your own hardware or VPS: what's your setup? Are you using a reverse proxy with automatic cert provisioning (Caddy, Traefik, nginx-proxy with acme-companion)? Have you settled on one approach, or do you mix and match depending on the service? Genuinely curious what's working for people who've been doing this longer than I have, especially when the number of services grows past what you can mentally track.
document fetched 2026-10-28 00:30 · canonical https://reddit.com/r/selfhosted/comments/1xgzsrv/how_do_you_handle_ssl_renewals_across_multiple