d7c4a89106
* Add max upstream connections dns-proxy option Allows defining a limit to the number of connections that can be established with the upstream DNS host. If left unset, there may be situations where connections fail to establish, which causes the Transport to create an influx of connections causing upstream to throttle our requests and triggering a runaway effect resulting in high CPU usage. See https://github.com/cloudflare/cloudflared/issues/91 * Code review with proposed changes * Add max upstream connections flag to tunnel flags * Reduce DNS proxy max upstream connections default value Reduce the default value of maximum upstream connections on the DNS proxy to guarantee it works on single-core and other low-end hardware. Further testing could allow for a safe increase of this value. * Update dns-proxy flag name Also remove `MaxUpstreamConnsFlag` const as it's no longer referenced in more than one place and to make things more consistent with how the other flags are referenced. Co-authored-by: Adam Chalmers <achalmers@cloudflare.com> |
||
---|---|---|
.mac_resources | ||
.teamcity | ||
buffer | ||
carrier | ||
certutil | ||
cmd/cloudflared | ||
connection | ||
dbconnect | ||
dbconnect_tests | ||
edgediscovery | ||
h2mux | ||
hello | ||
ingress | ||
logger | ||
metrics | ||
origin | ||
overwatch | ||
signal | ||
socks | ||
ssh_server_tests | ||
sshgen | ||
teamnet | ||
tlsconfig | ||
tunneldns | ||
tunnelrpc | ||
tunnelstore | ||
validation | ||
vendor | ||
watcher | ||
websocket | ||
.docker-images | ||
.dockerignore | ||
.gitignore | ||
Dockerfile | ||
LICENSE | ||
Makefile | ||
README.md | ||
RELEASE_NOTES | ||
cfsetup.yaml | ||
cloudflared_man_template | ||
dev.Dockerfile | ||
github_message.py | ||
github_release.py | ||
go.mod | ||
go.sum | ||
jet.yaml | ||
postinst.sh | ||
postrm.sh | ||
wix.json |
README.md
Argo Tunnel client
Contains the command-line client for Argo Tunnel, a tunneling daemon that proxies any local webserver through the Cloudflare network. Extensive documentation can be found in the Argo Tunnel section of the Cloudflare Docs.
Before you get started
Before you use Argo Tunnel, you'll need to complete a few steps in the Cloudflare dashboard. The website you add to Cloudflare will be used to route traffic to your Tunnel.
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.
- You can install on macOS via Homebrew or by downloading the latest Darwin amd64 release
- Binaries, Debian, and RPM packages for Linux can be found here
- A Docker image of
cloudflared
is available on DockerHub - You can install on Windows machines with the steps here
User documentation for Argo 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 that serve traffic for hostnames in your account.
- Create a Tunnel with these instructions
- Route traffic to that Tunnel with DNS records in Cloudflare or with a Cloudflare Load Balancer
TryCloudflare
Want to test Argo Tunnel before adding a website to Cloudflare? You can do so with TryCloudflare using the documentation available here.
Deprecated versions
Cloudflare currently supports all versions of cloudflared
. Starting on March 20, 2021, Cloudflare will no longer support versions released prior to 2020.5.1.
All features available in versions released prior to 2020.5.1 are available in current versions. 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 | Will no longer be supported starting March 20, 2021 |