Example: The following command runs the
mytunnel tunnel by proxying traffic to port
8000 and disabling chunked transfer encoding.
cloudflared tunnel --url localhost:8000 --no-chunked-encoding run mytunnel
Specifies the path to a config file in YAML format.
Disables periodic check for updates, restarting the server with the new version. See also: . Restarts are performed by spawning a new process that connects to the Cloudflare edge. On successful connection, the old process will gracefully shut down after handling all outstanding requests.
Specifies the Tunnel certificate for one of your zones, authorizing the client to serve as an origin for that zone. A certificate is required to use Cloudflare Tunnel. You can obtain a certificate by using the login command or by visiting
cloudflared receives SIGINT/SIGTERM it will stop accepting new requests, wait for in-progress requests to terminate, then shut down. Waiting for in-progress requests will timeout after this grace period, or when a second SIGTERM/SIGINT is received.
Specifies address to query for usage metrics.
Specifies frequency to update tunnel metrics.
Specifies custom tags used to identify this tunnel, in format
KEY=VALUE. Multiple tags may be specified by delimiting them with commas e.g.
Specifies the maximum number of retries for connection/protocol errors. Retries use exponential backoff (retrying at 1, 2, 4, 8, 16 seconds by default), so it is not recommended that you increase this value significantly.
Writes the application’s process identifier (PID) to this file after the first successful connection. Mainly useful for scripting and service integration.
Specifies the protocol used to establish a connection between
cloudflared and the edge. Available values are
auto value will automatically configure the
Allows you to choose the regions to which connections are established. Omit or leave empty to connect to the global region. Set
--region=us to route all connections through us region 1 and us region 2.
Specifies the verbosity of logging. The default
info level does not produce much output, but you may wish to use the
warn level in production. Available levels are:
Specifies the verbosity of logs for the transport between
cloudflared and the Cloudflare edge. Available levels are:
Any value below
warn produces substantial output and should only be used to debug low-level performance issues and protocol quirks.