Recover: Caddy (reverse proxy)
No signal criticalTLS termination and public routing. Managed configuration — treated as read-only by JarvisOS tooling.
- Owner
- homelab-operator
- Target RTO
- 10m
- Last heartbeat
- never
- Dependent entities
- 0
Recovery readiness20/100
Procedure
Read fully before acting.- The Caddyfile is managed configuration. Do not edit it during incident response.
- Validate before reloading; a reload with a bad config drops every published route at once.
- Certificate renewal failures usually trace back to DNS, not to Caddy — check cloudflare-dns first.
Bring-up order
Dependencies first — starting out of order is a common second incident.- VIN / VPS Node
- ISP Uplink Dependency
- Public DNS DNS
- Caddy (reverse proxy) Service target
Readiness breakdown
- Documented runbook 20 pts
- No backup configured 50 pts
- No failover target configured 30 pts