====== Named Tunnels Use Remote Configuration ======

**DEPRECATED:** This guide is no longer relevant for folk.zone. The nitro server uses direct HTTPS via Let's Encrypt instead of Cloudflare tunnels.

**Affects:** [[folkzone:services:cloudflared|Cloudflare Tunnel]]

===== Fact =====

When ''config.yml'' contains a ''tunnel:'' field with a tunnel ID, cloudflared ignores local ''ingress:'' rules entirely. Configuration is pulled from Cloudflare's servers.

The local ''config.yml'' is only used for:
  * Credentials file path (''credentials-file'')
  * Basic runtime settings (''no-autoupdate'', etc.)

**Ingress rules must be managed through the Zero Trust dashboard.**

===== Implication =====

Editing ''ingress:'' entries in the local config file and restarting cloudflared will have no effect. The container will log ''Updated to new configuration'' using the remote config, silently ignoring local changes.

===== See Also =====
  * [[folkzone:troubleshooting:start|Homelab Troubleshooting Index]]

  * [[folkzone:troubleshooting:cloudflare_add_hostname|Adding a Hostname to a Named Tunnel]]
  * [[folkzone:troubleshooting:cloudflare_dns_vs_route|DNS Records vs. Tunnel Routes Are Different Things]]
  * [[folkzone:services:cloudflared|Cloudflare Tunnel]]
  * [[start|Return to wiki home]]