Go to file
Devin Carr 978e01f77e TUN-6010: Add component tests for --edge-ip-version 2022-06-14 16:57:59 +00:00
.github
.mac_resources
.teamcity TUN-6197: Publish to brew core should not try to open the browser 2022-05-11 15:26:05 +01:00
carrier carrier: fix dropped errors 2022-03-30 07:09:09 -07:00
certutil Fix typos 2021-11-12 17:38:06 +02:00
cfapi TUN-5915: New cloudflared command to allow to retrieve the token credentials for a Tunnel 2022-03-23 10:35:16 +00:00
cfio
cmd/cloudflared
component-tests TUN-6010: Add component tests for --edge-ip-version 2022-06-14 16:57:59 +00:00
config TUN-6293: Update yaml v3 to latest hotfix 2022-05-30 17:38:55 +00:00
connection TUN-6385: Don't share err between acceptStream loop and per-stream goroutines 2022-06-13 18:24:00 -05:00
datagramsession
edgediscovery
fips
h2mux TUN-5551: Reintroduce FIPS compliance for linux amd64 now as separate binaries 2021-12-20 21:50:42 +00:00
hello
ingress TUN-6293: Update yaml v3 to latest hotfix 2022-05-30 17:38:55 +00:00
ipaccess
logger TUN-4067: Reformat code for consistent import order, grouping, and fix formatting. Added goimports target to the Makefile to make this easier in the future. 2021-03-24 10:53:29 -05:00
metrics TUN-6357: Add connector id to ready check endpoint 2022-06-08 17:35:23 +00:00
orchestration TUN-6016: Push local managed tunnels configuration to the edge 2022-05-06 15:43:24 +00:00
overwatch
proxy
quic
retry TUN-3863: Consolidate header handling logic in the connection package; move headers definitions from h2mux to packages that manage them; cleanup header conversions 2021-03-29 21:57:56 +00:00
signal TUN-1562: Refactor connectedSignal to be safe to close multiple times 2019-03-05 15:51:35 -06:00
socks
ssh_server_tests
sshgen
supervisor TUN-6384: Correct duplicate connection error to fetch new IP first 2022-06-14 15:40:58 +00:00
tlsconfig TUN-5612: Make tls min/max version public visible 2022-01-03 18:13:57 +00:00
token
tracing TUN-6250: Add upstream response status code to tracing span attributes 2022-05-18 15:40:48 +01:00
tunneldns
tunnelrpc
tunnelstate TUN-5368: Log connection issues with LogLevel that depends on tunnel state 2021-11-10 09:00:05 +00:00
validation
vendor
watcher
websocket
.docker-images
.dockerignore
.gitignore
CHANGES.md
Dockerfile
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 AUTH-2858: Set file to disable autoupdate 2020-07-10 18:03:07 +00:00
postrm.sh
release_pkgs.py TUN-6361: Add cloudflared arm builds to pkging as well 2022-06-08 15:59:36 +01:00
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