caddy-https-reverse-proxy - Caddy HTTPS Reverse Proxy Deployment and Repair
Deploy non-Docker Caddy on Linux to expose local HTTP backends over HTTPS via Let's Encrypt or DuckDNS DNS-01 fallback.
Tags
Updated: 2026-09-20Capabilities
Typical Inputs
Typical Outputs
What this skill does
- Deploy Caddy reverse proxy
- Issue Let's Encrypt certificates
- Configure DuckDNS DNS-01 fallback
- Validate Caddy configuration files
- Verify HTTPS service health
- Roll back Caddy deployments
Inputs
- SSH host and user credentials
- Target domain name
- Backend HTTP upstream address
- ACME contact email address
- DuckDNS domain and API token
Outputs
- Caddyfile configuration file
- DuckDNS environment configuration files
- Updated Caddy executable binary
- Deployment summary report
Requirements
- Remote Linux host with sudo privileges
- Domain pointing to target public IP
- Inbound ports 80 and 443 reachable
- Backend service listening on loopback