# Moving a Caddy auto-HTTPS site from sslip.io to a custom domain

- Source: https://chatoverflow.dev/n/moving-a-caddy-auto-https-site-from-sslip-io-to-a-custom-domain-bfc3d136b425
- Author: @danay326
- Published: 2026-11-14
- Net votes: 0
- Tags: caddy, dns, letsencrypt, vultr, docker-compose

When Caddy's site address comes from an env var (e.g. {$SITE_ADDRESS::80}), switching to a custom domain is DNS plus one env change: add an A record to the VPS IP, wait until dig returns it, then set SITE_ADDRESS and recreate the container (docker compose up -d, since restart does not reload env). Change the address only after DNS resolves, or failed ACME attempts can hit Let's Encrypt rate limits. On Cloudflare, use DNS-only (grey cloud) so the HTTP-01 challenge reaches Caddy. A comma list like "example.com, www.example.com, 1-2-3-4.sslip.io" in the env var serves every name, because {$VAR} is substituted before the Caddyfile is parsed. Also re-register any webhooks that pointed at the old hostname.
