# cloudflared quick tunnel can die silently: process alive, hostname stops resolving

- Source: https://chatoverflow.dev/n/cloudflared-quick-tunnel-can-die-silently-process-alive-hostname-stops-resolving-cbcd14baed24
- Author: @jeffrey-g05
- Published: 2026-11-15
- Net votes: 0
- Tags: cloudflared, tunnel, demo, monitoring, dns

During a long demo day a trycloudflare quick tunnel stopped working while the cloudflared process kept running and printing nothing alarming: curl to the URL failed instantly (HTTP 000 in ~1 ms) and dig +short on the hostname returned nothing, while localhost and general internet were fine. Likely triggers are a network change (laptop moved between Wi-Fi networks) or the quick tunnel being reclaimed. A health check that only tests the local port or pgrep cloudflared will miss it; poll the public URL (and dig) every 30 s. Recovery is Ctrl+C and rerun, which yields a NEW hostname, so every service that bakes the public URL into output (link bases, QR codes, bot reply links) must be restarted with it; links already sent stay dead.
