Go to file
Nuno Diegues 7607ead143 TUN-6503: Fix transport fallback from QUIC in face of dial error "no network activity" 2022-07-06 13:05:45 +01:00
.github TUN-6414: Remove go-sumtype from cloudflared build process 2022-06-17 09:23:44 +01:00
.mac_resources AUTH-2712 mac package build script and better config file handling when started as a service 2020-06-25 16:44:57 -05:00
.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 TUN-6035: Reduce buffer size when proxying data 2022-04-11 14:41:33 +00:00
cmd/cloudflared TUN-6503: Fix transport fallback from QUIC in face of dial error "no network activity" 2022-07-06 13:05:45 +01:00
component-tests TUN-6010: Add component tests for --edge-ip-version 2022-06-23 16:55:03 +00:00
config Merge pull request #656 from nikr-canva/http2-origins 2022-06-16 12:23:07 -05:00
connection TUN-6460: Rename metric label location to edge_location 2022-06-24 09:46:22 -07:00
datagramsession TUN-6301: Allow to update logger used by UDP session manager 2022-05-30 13:53:27 +00:00
edgediscovery TUN-6388: Fix first tunnel connection not retrying 2022-06-23 16:55:03 +00:00
fips TUN-3905: Cannot run go mod vendor in cloudflared due to fips 2021-03-09 17:31:59 +04:00
h2mux TUN-5551: Reintroduce FIPS compliance for linux amd64 now as separate binaries 2021-12-20 21:50:42 +00:00
hello TUN-5164: Update README and clean up references to Argo Tunnel (using Cloudflare Tunnel instead) 2021-09-29 08:27:47 +00:00
ingress Merge pull request #656 from nikr-canva/http2-origins 2022-06-16 12:23:07 -05:00
ipaccess TUN-6016: Push local managed tunnels configuration to the edge 2022-05-06 15:43:24 +00:00
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-6380: Enforce connect and keep-alive timeouts for TCP connections in both WARP routing and websocket based TCP proxy. 2022-06-14 21:36:40 +00:00
overwatch AUTH-2169 make access login page more generic 2020-06-08 11:20:30 -05:00
proxy TUN-6427: Differentiate between upstream request closed/canceled and failed origin requests 2022-06-20 14:29:53 +00:00
quic TUN-6499: Remove log that is per datagram 2022-07-05 18:06:37 +01:00
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 Fix typos 2021-11-12 17:38:06 +02:00
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
supervisor TUN-6503: Fix transport fallback from QUIC in face of dial error "no network activity" 2022-07-06 13:05:45 +01:00
tlsconfig TUN-5612: Make tls min/max version public visible 2022-01-03 18:13:57 +00:00
token TUN-6459: Add cloudflared user-agent to access calls 2022-06-24 11:51:53 -07:00
tracing TUN-6250: Add upstream response status code to tracing span attributes 2022-05-18 15:40:48 +01:00
tunneldns TUN-5675: Remove github.com/dgrijalva/jwt-go dependency by upgrading coredns version 2022-01-25 15:24:13 +00:00
tunnelrpc TUN-6016: Push local managed tunnels configuration to the edge 2022-05-06 15:43:24 +00:00
tunnelstate TUN-5368: Log connection issues with LogLevel that depends on tunnel state 2021-11-10 09:00:05 +00:00
validation TUN-5164: Update README and clean up references to Argo Tunnel (using Cloudflare Tunnel instead) 2021-09-29 08:27:47 +00:00
vendor TUN-6191: Update quic-go to v0.27.1 and with custom patch to allow keep alive period to be configurable 2022-06-07 12:25:18 +01:00
watcher TUN-5551: Reintroduce FIPS compliance for linux amd64 now as separate binaries 2021-12-20 21:50:42 +00:00
websocket TUN-6035: Reduce buffer size when proxying data 2022-04-11 14:41:33 +00:00
.docker-images
.dockerignore
.gitignore
CHANGES.md
Dockerfile
LICENSE
Makefile TUN-6362: Add armhf support to cloudflare packaging 2022-06-20 12:05:03 +01:00
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 TUN-6191: Update quic-go to v0.27.1 and with custom patch to allow keep alive period to be configurable 2022-06-07 12:25:18 +01:00
go.sum
jet.yaml
postinst.sh
postrm.sh
release_pkgs.py
wix.json AUTH-2712 mac package build script and better config file handling when started as a service 2020-06-25 16:44:57 -05:00

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