Domains, HTTPS & email

Server Manager picks Caddy as the [[reverse-proxy]] because automatic HTTPS works in zero config — type a domain, get a valid cert 30 seconds later. nginx and Apache need certbot + a renewal cron + manual reloads to get there. Caddy collapses all of that into "type domain, get HTTPS." This article compares Caddy, nginx, Apache, and Traefik feature-by-feature, explains the rationale, and tells you when keeping your current engine is the right call.

Point a domain you own at your server and get free HTTPS. The wizard probes where the domain currently lives and walks you through whatever's missing — DNS record, Cloudflare/Porkbun token, Let's Encrypt certificate.

One-click recipe that translates your existing reverse-proxy config to a Caddyfile, rehearses on alternate ports while the old engine keeps serving live traffic, then atomically swaps. Auto-rollback fires if anything fails verification. After migration, every Server Manager flow (deploy, connect-domain, install WordPress, …) works directly instead of routing through the chat fallback.

Two separate surfaces — Send (apps emailing FROM your domain) and Receive (mail addressed TO your domain). Walks through both wizards and explains which one you need.