Caddy reverse proxy guide
Optional in-guest Caddy for path routing; prefer multiple platform sites for separate Hosts.

Do I need Caddy?
No, not for HTTPS. Every NairaCloud node already runs a Caddy edge on ports 80/443. It terminates TLS and forwards plain HTTP to each site's origin port. Prefer multiple platform sites (different labels) when apps need separate Hosts. Use Caddy inside the instance only for path routing behind one origin.
Quick start (inside the instance)
Bind Caddy to 8080 inside the instance, then set that as the site origin port in the dashboard. Do not map 80/443 in the container.
Common patterns
Reverse proxy
Static site with SPA fallback
Path-based routing
WebSocket upgrade
Load balancing
TLS and domains
Leave certificates to the platform edge. A custom domain is attached in the dashboard, not in this Caddyfile. If you put your own TLS-terminating proxy in front of the instance, it must speak plain HTTP to the platform edge or use a published TCP port instead.
Troubleshooting
Practical -- try it now
Caddy is serving your containers
- Start Caddy on port 8080 with the Caddyfile above.
- In Sites, set the web origin to 8080.
- Open the HTTPS URL -- the platform edge terminates TLS and Caddy routes internally.