Certificate renewal checks for small Caddy hosts
Before blaming ACME, check DNS, port 80, the active Caddyfile, and whether another service owns 443. For edge servers, keeping the HTTP challenge path reachable is often enough.
Field notes
Brief notes are kept here so repeat jobs can start from a known checklist instead of a blank terminal.
Before blaming ACME, check DNS, port 80, the active Caddyfile, and whether another service owns 443. For edge servers, keeping the HTTP challenge path reachable is often enough.
One useful page lists public hostnames, listeners, service files, config paths, certificate stores, backup locations, and the exact command used to reload each daemon.
A small technical service page rarely needs a database. Static files, cacheable assets, and a boring web server usually provide better uptime and easier recovery.
Access logs, error logs, and service journal output are usually enough to locate a broken redirect, expired certificate, or wrong root path.