Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Configure Caddy as a reverse proxy with automatic HTTPS and simple Caddyfile syntax.
Configure Caddy as a reverse proxy with automatic HTTPS and simple Caddyfile syntax.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Caddy provisions SSL certificates automatically โ don't manually configure Let's Encrypt unless you have specific needs Domain must resolve to the server publicly for HTTP challenge โ use DNS challenge for internal/wildcard certs Ports 80 and 443 must be free โ Caddy needs both even for HTTPS-only (80 handles ACME challenges and redirects) Let's Encrypt has rate limits โ use staging CA during testing to avoid hitting production limits
Indentation is significant โ blocks are defined by indentation, not braces in shorthand Site blocks need a space before the opening brace: example.com { not example.com{ Use caddy fmt --overwrite to fix formatting โ catches most syntax issues Validate before applying: caddy validate --config /etc/caddy/Caddyfile
Caddy adds X-Forwarded-For, X-Forwarded-Proto, X-Forwarded-Host automatically โ don't add them manually WebSocket works out of the box โ no special configuration needed Load balancing is automatic with multiple backends โ default is random, use lb_policy to change Passive health checks remove failed backends automatically
Use container names as hostnames: reverse_proxy container_name:3000 Caddy and backends must share a Docker network โ default bridge doesn't support DNS resolution For Docker Compose, service names work as hostnames when on the same network
Use caddy reload not restart โ reload applies changes without dropping connections Config changes are atomic โ if new config fails validation, old config stays active Test without applying: caddy adapt --config Caddyfile shows parsed JSON output
Certificates stored in ~/.local/share/caddy by default โ preserve this across reinstalls For Docker, mount volumes for /data and /config โ losing these means re-requesting all certificates Multiple Caddy instances need shared storage or will fight over certificates
Enable debug logging: add debug as first line in global options block Check certificate status in /data/caddy/certificates/ directory Common issue: DNS not pointing to server yet โ certificates fail silently until domain resolves
Caddy doesn't add security headers by default โ add X-Frame-Options, X-Content-Type-Options explicitly HSTS is automatic when serving HTTPS โ no manual configuration needed
Handles thousands of concurrent connections without tuning HTTP/3 available with servers { protocols h1 h2 h3 } Compression automatic for text content
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.