troubleshooting:cloudflare_add_hostname
Table of Contents
Adding a Hostname to a Named Tunnel
DEPRECATED: This guide is no longer relevant for folk.zone. The nitro server uses direct HTTPS via Let's Encrypt instead of Cloudflare tunnels.
Status: Resolved
Affects: Cloudflare Tunnel
The only correct way to add a new subdomain route to a Named Tunnel is through the Cloudflare Zero Trust dashboard.
Steps
- Zero Trust → Networks → Tunnels →
cafe - Public Hostnames → Add a public hostname
- Fill in:
- Subdomain:
service - Domain:
folk.zone - Service:
http://caddy:80
- Save
Cloudflare automatically creates the DNS CNAME record. No manual DNS entry needed.
If you get "DNS record already exists"
Delete the existing DNS record first (DNS tab → delete the CNAME), then add the public hostname through Zero Trust. Cloudflare will recreate the DNS record correctly.
What happens after saving
- Cloudflare pushes the new ingress rule to the remote tunnel config
- The running cloudflared container pulls the update automatically (no restart needed)
- Route becomes active within seconds
See Also
troubleshooting/cloudflare_add_hostname.txt · Last modified: by 127.0.0.1
