Cloudflare Update Notes

Overview

When a tunnel is already running, a new hostname usually needs three coordinated changes: a DNS CNAME in Cloudflare, an ingress entry in the local tunnel config, and a clean restart or reload of the tunnel process.

Working Assumptions

Step 1: Create DNS

Add a proxied CNAME for the new subdomain that points at the tunnel endpoint. Prefer the Cloudflare API when available; otherwise create the record in the dashboard.

POST /zones/<ZONE_ID>/dns_records

{
  "type": "CNAME",
  "name": "app",
  "content": "<TUNNEL_ID>.cfargotunnel.com",
  "proxied": true,
  "ttl": 1
}

Step 2: Update Ingress

Edit the tunnel config and insert the new hostname before the catch-all rule. Keep indentation exact.

tunnel: <TUNNEL_ID>

ingress:
  - hostname: app.example.com
  - service: http_status:404

Step 3: Restart And Verify

1. Restart or reload the tunnel process so the new ingress rule is active.
2. Confirm the process registers healthy tunnel connections.
3. Request https://app.example.com and confirm a sensible HTTP response and Cloudflare headers.

Troubleshooting Themes

• DNS lag — wait briefly, then re-check that the CNAME target matches <TUNNEL_ID>.cfargotunnel.com.
• Bad gateway responses — confirm the upstream behind the hostname is reachable and that the ingress hostname matches the DNS name.
• Config ignored — verify YAML structure, save the file, and restart the tunnel process.
• Tunnel won't start — re-check tunnel ID, config syntax, and that the process was restarted after the last edit.

Operating Reminder