Go to file
Devin Carr 7a014b06ec TUN-7129: Categorize TCP logs for streaming logs 2023-04-18 20:49:29 +00:00
.github
.mac_resources
.teamcity EDGESTORE-108: Remove deprecated s3v2 signature 2023-03-09 18:24:42 +00:00
carrier
cfapi
cfio TUN-6035: Reduce buffer size when proxying data 2022-04-11 14:41:33 +00:00
cmd/cloudflared
component-tests TUN-7360: Add Get Host Details handler in management service 2023-04-18 09:54:54 +00:00
config
connection
credentials TUN-7134: Acquire token for cloudflared tail 2023-04-12 09:43:38 -07:00
datagramsession TUN-6829: Allow user of datagramsession to control logging level of errors 2022-10-11 18:49:02 +00:00
edgediscovery
features TUN-7131: Add cloudflared log event to connection messages and enable streaming logs 2023-04-12 14:41:11 -07:00
fips RTG-1339 Support post-quantum hybrid key exchange 2022-09-07 19:32:53 +00:00
h2mux TUN-5551: Reintroduce FIPS compliance for linux amd64 now as separate binaries 2021-12-20 21:50:42 +00:00
hello
ingress
internal/test
ipaccess TUN-6016: Push local managed tunnels configuration to the edge 2022-05-06 15:43:24 +00:00
logger TUN-7127: Disconnect logger level requirement for management 2023-04-06 11:31:47 -07:00
management TUN-7360: Add Get Host Details handler in management service 2023-04-18 09:54:54 +00:00
metrics TUN-7147: Revert wrong removal of debug endpoint from metrics port 2023-01-31 11:51:29 +00:00
orchestration
overwatch AUTH-2169 make access login page more generic 2020-06-08 11:20:30 -05:00
packet ZTC-234: Replace ICMP funnels when ingress connection changes 2022-11-11 19:43:26 +00:00
proxy TUN-7129: Categorize TCP logs for streaming logs 2023-04-18 20:49:29 +00:00
quic
retry
signal TUN-1562: Refactor connectedSignal to be safe to close multiple times 2019-03-05 15:51:35 -06:00
socks
ssh_server_tests Fix typos 2021-11-12 17:38:06 +02:00
sshgen CC-796: Remove dependency on unsupported version of go-oidc 2022-03-18 18:16:10 +00:00
stream TUN-7057: Remove dependency github.com/gorilla/mux 2022-12-24 21:05:51 -07:00
supervisor TUN-7131: Add cloudflared log event to connection messages and enable streaming logs 2023-04-12 14:41:11 -07:00
tlsconfig
token TUN-6917: Bump go to 1.19.3 2022-11-07 09:19:19 -08:00
tracing TUN-7197: Add connIndex tag to debug messages of incoming requests 2023-02-22 16:08:24 +00:00
tunneldns
tunnelrpc TUN-6917: Bump go to 1.19.3 2022-11-07 09:19:19 -08:00
tunnelstate TUN-6617: Dont fallback to http2 if QUIC conn was successful. 2022-08-12 08:40:03 +00:00
validation
vendor TUN-7356: Bump golang.org/x/net package to 0.7.0 2023-04-07 09:41:23 -07:00
watcher
websocket
.docker-images
.dockerignore
.gitignore
CHANGES.md
Dockerfile
Dockerfile.amd64
Dockerfile.arm64
LICENSE TUN-5851: Update all references to point to Apache License 2.0 2022-03-08 17:35:31 +00:00
Makefile
README.md
RELEASE_NOTES
build-packages-fips.sh
build-packages.sh
cfsetup.yaml
check-fips.sh
cloudflared.wxs
cloudflared_man_template
dev.Dockerfile
fmt-check.sh
github_message.py
github_release.py
go.mod
go.sum
jet.yaml
postinst.sh
postrm.sh
release_pkgs.py
wix.json

README.md

Cloudflare Tunnel client

Contains the command-line client for Cloudflare Tunnel, a tunneling daemon that proxies traffic from the Cloudflare network to your origins. This daemon sits between Cloudflare network and your origin (e.g. a webserver). Cloudflare attracts client requests and sends them to you via this daemon, without requiring you to poke holes on your firewall --- your origin can remain as closed as possible. Extensive documentation can be found in the Cloudflare Tunnel section of the Cloudflare Docs. All usages related with proxying to your origins are available under cloudflared tunnel help.

You can also use cloudflared to access Tunnel origins (that are protected with cloudflared tunnel) for TCP traffic at Layer 4 (i.e., not HTTP/websocket), which is relevant for use cases such as SSH, RDP, etc. Such usages are available under cloudflared access help.

You can instead use WARP client to access private origins behind Tunnels for Layer 4 traffic without requiring cloudflared access commands on the client side.

Before you get started

Before you use Cloudflare Tunnel, you'll need to complete a few steps in the Cloudflare dashboard: you need to add a website to your Cloudflare account. Note that today it is possible to use Tunnel without a website (e.g. for private routing), but for legacy reasons this requirement is still necessary:

  1. Add a website to Cloudflare
  2. Change your domain nameservers to Cloudflare

Installing cloudflared

Downloads are available as standalone binaries, a Docker image, and Debian, RPM, and Homebrew packages. You can also find releases here on the cloudflared GitHub repository.

User documentation for Cloudflare Tunnel can be found at https://developers.cloudflare.com/cloudflare-one/connections/connect-apps

Creating Tunnels and routing traffic

Once installed, you can authenticate cloudflared into your Cloudflare account and begin creating Tunnels to serve traffic to your origins.

TryCloudflare

Want to test Cloudflare Tunnel before adding a website to Cloudflare? You can do so with TryCloudflare using the documentation available here.

Deprecated versions

Cloudflare currently supports versions of cloudflared 2020.5.1 and later. Breaking changes unrelated to feature availability may be introduced that will impact versions released prior to 2020.5.1. You can read more about upgrading cloudflared in our developer documentation.

Version(s) Deprecation status
2020.5.1 and later Supported
Versions prior to 2020.5.1 No longer supported