====== 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:** [[folkzone:services:cloudflared|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 =====
  * [[folkzone:troubleshooting:start|Homelab Troubleshooting Index]]

  * [[folkzone:troubleshooting:cloudflare_named_tunnel_remote_config|Named Tunnels Use Remote Configuration]]
  * [[folkzone:troubleshooting:cloudflare_dns_vs_route|DNS Records vs. Tunnel Routes Are Different Things]]
  * [[guides:add_new_service|Adding a New Service]]
  * [[start|Return to wiki home]]