Cloudflare Tunnel

Help us improve your experience.

The Cloudflare Zero Trust docs team is running a brief 10-question survey from June 5, 2025 to July 5, 2025 to learn how well the documentation is working for you, and where we can do better.

Take the survey ↗ and share your feedback directly with Cloudflare.

Subscribe to RSS

2024-12-19

Troubleshoot tunnels with diagnostic logs

The latest cloudflared build 2024.12.2 ↗ introduces the ability to collect all the diagnostic logs needed to troubleshoot a cloudflared instance.

A diagnostic report collects data from a single instance of cloudflared running on the local machine and outputs it to a cloudflared-diag file.

The cloudflared-diag-YYYY-MM-DDThh-mm-ss.zip archive contains the files listed below. The data in a file either applies to the cloudflared instance being diagnosed (diagnosee) or the instance that triggered the diagnosis (diagnoser). For example, if your tunnel is running in a Docker container, the diagnosee is the Docker instance and the diagnoser is the host instance.

File name	Description	Instance
cli-configuration.json	Tunnel run parameters used when starting the tunnel	diagnosee
cloudflared_logs.txt	Tunnel log file1	diagnosee
configuration.json	Tunnel configuration parameters	diagnosee
goroutine.pprof	goroutine profile made available by pprof	diagnosee
heap.pprof	heap profile made available by pprof	diagnosee
metrics.txt	Snapshot of Tunnel metrics at the time of diagnosis	diagnosee
network.txt	JSON traceroutes to Cloudflare's global network using IPv4 and IPv6	diagnoser
raw-network.txt	Raw traceroutes to Cloudflare's global network using IPv4 and IPv6	diagnoser
systeminformation.json	Operating system information and resource usage	diagnosee
task-result.json	Result of each diagnostic task	diagnoser
tunnelstate.json	Tunnel connections at the time of diagnosis	diagnosee

Footnotes

1. If the log file is blank, you may need to set --loglevel to debug when you start the tunnel. The --loglevel parameter is only required if you ran the tunnel from the CLI using a cloudflared tunnel run command. It is not necessary if the tunnel runs as a Linux/macOS service or runs in Docker/Kubernetes. ↩

For more information, refer to Diagnostic logs.

2024-10-17

Simplifed WARP Connector deployment

You can now deploy WARP Connector using a simplified, guided workflow similar to cloudflared connectors. For detailed instructions, refer to the WARP Connector documentation.

2024-10-10

Bugfix for --grace-period

The new cloudflared build 2024.10.0 ↗ has a bugfix related to the --grace-period tunnel run parameter. cloudflared connectors will now abide by the specified waiting period before forcefully closing connections to Cloudflare's network.

2024-08-06

cloudflared builds available in GitHub for Apple silicon

macOS users can now download cloudflared-arm64.pkg directly from GitHub ↗, in addition to being available via Homebrew.