All tunnel-related commands are prefixed with
tunnel. For example:
cloudflared tunnel --url localhost:5555 --hostname x.example.com
Specifies a config file in YAML format.
Connects to the local webserver at
Sets a hostname on a Cloudflare zone to route traffic through this tunnel.
Add this tunnel to a Load Balancer pool. If it doesn’t already exist a load balancer will be created for the hostname of your tunnel, and a pool will be created with the pool name you specify. Traffic destined to that pool will be load balanced across this tunnel and any other tunnels which share its pool name.
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 Argo Tunnel. You can obtain a certificate by using the login command or by visiting
Disables TLS verification of the certificate presented by your origin. Will allow any certificate from the origin to be accepted. The connection from your machine to Cloudflare's Edge is still encrypted and verified using TLS.
Path to the CA for the certificate of your origin. This option should be used only if your certificate is not signed by Cloudflare.
Address to query for usage metrics.
Frequency to update tunnel metrics.
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 verbosity of logging. The default
info is not noisy, but you may wish to run with
warn in production.
Specifies the verbosity of the HTTP/2 protocol logging. Any value below
warn is noisy and should only be used to debug low-level performance issues and protocol quirks.
Maximum number of retries for connection/protocol errors. Retries use exponential backoff (retrying at 1, 2, 4, 8, 16 seconds by default) so increasing this value significantly is not recommended.
Disables chunked transfer encoding; useful if you are running a WSGI server.
Use the established tunnel to expose a
Hello world HTTP server for testing Argo Tunnel. Mutually exclusive with the
Write the application's PID to this file after the first successful connection. Mainly useful for scripting and service integration.
Save application log to this file. Mainly useful for reporting issues.
Timeout for completing a TLS handshake to your origin server, if you have chosen to connect Tunnel to an HTTPS server.
The timeout after which a TCP keepalive packet is sent on a connection between Tunnel and the origin server.
Disable the "happy eyeballs" algorithm for IPv4/IPv6 fallback if your local network has misconfigured one of the protocols.
Maximum number of idle keepalive connections between Tunnel and your origin. This does not restrict the total number of concurrent connections.
Timeout after which an idle keepalive connection can be discarded.
Shows help text.
Prints the version number and build date.
cloudflared tunnel login
Opens a special section of the Cloudflare dashboard for obtaining a Tunnel certificate.
It should open your browser automatically and prompt you to log in to your Cloudflare account (unless you previously logged in with 'Remember me' selected). If running cloudflared on a server, you will be given an URL that you can visit on another machine.
After logging in, a list of your zones will appear. Select the zone you want to use Argo Tunnel with. After confirming your authorization, the certificate should be sent to the Tunnel client and saved to
.cloudflared/cert.pem in your user folder. If this process fails for any reason, the certificate will instead be downloaded by your browser and you will have to copy the file manually to that location.
You can also obtain a Tunnel certificate independently of this command by visiting
cloudflared service install
cloudflared service uninstall
Install or uninstall cloudflared as a system service. The details of service installation depend on the OS you are using.
Looks for a new version on the official download server. If a new version exists, updates the agent binary and quits. Otherwise, it does nothing. To determine if an update happened in a script, check for error code 64.