- Starting from this version, tunnel diagnostics will be enabled by default. This will allow the engineering team to remotely get diagnostics from cloudflared during debug activities. Users still have the capability to opt-out of this feature by defining
--management-diagnostics=false(or envTUNNEL_MANAGEMENT_DIAGNOSTICS).
- The
warp-routingenabled: booleanflag is no longer supported in the configuration file. Warp Routing traffic (eg TCP, UDP, ICMP) traffic is proxied to cloudflared if routes to the target tunnel are configured. This change does not affect remotely managed tunnels, but for locally managed tunnels, users that might be relying on this feature flag to block traffic should instead guarantee that tunnel has no Private Routes configured for the tunnel.
- You can now enable additional diagnostics over the management.argotunnel.com service for your active cloudflared connectors via a new runtime flag
--management-diagnostics(or envTUNNEL_MANAGEMENT_DIAGNOSTICS). This feature is provided as opt-in and requires the flag to enable. Endpoints such as /metrics provides your prometheus metrics endpoint another mechanism to be reached. Additionally /debug/pprof/(goroutine|heap) are also introduced to allow for remotely retrieving active pprof information from a running cloudflared connector.
- You can now stream your logs from your remote cloudflared to your local terminal with
cloudflared tail <TUNNEL-ID>. This new feature requires the remote cloudflared to be version 2023.4.1 or higher.
- Due to the nature of QuickTunnels (https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/do-more-with-tunnels/trycloudflare/) and its intended usage for testing and experiment of Cloudflare Tunnels, starting from 2023.3.2, QuickTunnels only make a single connection to the edge. If users want to use Tunnels in a production environment, they should move to Named Tunnels instead. (https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/tunnel-guide/remote/#set-up-a-tunnel-remotely-dashboard-setup)
- Running a tunnel without ingress rules defined in configuration file nor from the CLI flags will no longer provide a default ingress rule to localhost:8080 and instead will return HTTP response code 503 for all incoming HTTP requests.
- Windows 32 bit machines MSI now defaults to Program Files to install cloudflared. (See CVE-2023-1314). The cloudflared client itself is unaffected. This just changes how the installer works on 32 bit windows machines.
- Fixed a bug that would cause running tunnel on Bastion mode and without ingress rules to crash.
- Legacy tunnels were officially deprecated on December 1, 2022. Starting with this version, cloudflared no longer supports connecting legacy tunnels.
- h2mux tunnel connection protocol is no longer supported. Any tunnels still configured to use this protocol will alert and use http2 tunnel protocol instead. We recommend using quic protocol for all tunnels going forward.
- Fixed a bug in TCP connection proxy that could result in the connection being closed before all data was written.
- cloudflared now correctly aborts body write if connection to origin service fails after response headers were sent already.
- Fixed a bug introduced in the previous release where debug endpoints were removed.
- cloudflared now attempts to try other edge addresses before falling back to a lower protocol.
- cloudflared tunnel no longer spins up a quick tunnel. The call has to be explicit and provide a --url flag.
- cloudflared will now randomly pick the first or second region to connect to instead of always connecting to region2 first.
- cloudflared now rejects ingress rules with invalid http status codes for http_status.
- cloudflared now remembers if it connected to a certain protocol successfully. If it did, it does not fall back to a lower protocol on connection failures.
- It is now possible to connect cloudflared tunnel to Cloudflare Global Network with IPv6. See
cloudflared tunnel --helpand look foredge-ip-versionfor more information. For now, the default behavior is to still connect with IPv4 only.
- Several bug fixes related with QUIC transport (used between cloudflared tunnel and Cloudflare Global Network). Updating to this version is highly recommended.
cloudflared tunnel runno longer logs the Tunnel token or JSON credentials in clear text as those are the secret that allows to run the Tunnel.
- It is now possible to retrieve the credentials that allow to run a Tunnel in case you forgot/lost them. This is
achievable with:
cloudflared tunnel token --cred-file /path/to/file.json TUNNEL. This new feature only works for Tunnels created with cloudflared version 2022.3.0 or more recent.
cloudflared service installnow starts the underlying agent service on Linux operating system (similarly to the behaviour in Windows and MacOS).
cloudflared service installnow starts the underlying agent service on Windows operating system (similarly to the behaviour in MacOS).
- Various fixes to the reliability of
quicprotocol, including an edge case that could lead to cloudflared crashing.
- It is now possible to configure Ingress Rules to point to an origin served by unix socket with either HTTP or HTTPS.
If the origin starts with
unix:/then we assume HTTP (existing behavior). Otherwise, the origin can start withunix+tls:/for HTTPS.
- This project now has a new LICENSE that is more compliant with open source purposes.
- Various fixes to the reliability of
quicprotocol.
- New
cloudflared tunnel vnetcommands to allow for private routing to be virtualized. This means that the same CIDR can now be used to point to two different Tunnels withcloudflared tunnel route ipcommand. More information will be made available on blog.cloudflare.com and developers.cloudflare.com/cloudflare-one once the feature is globally available.
- Correctly handle proxying UDP datagrams with no payload.
- Bug fix for origins that use Server-Sent Events (SSE).
- If a specific
protocolproperty is defined (e.g. forquic), cloudflared no longer falls back to an older protocol (such ashttp2) in face of connectivity errors. This is important because some features are only supported in a specific protocol (e.g. UDP proxying only works forquic). Hence, if a user chooses a protocol, cloudflared now adheres to it no matter what.
- Stopping cloudflared running with
quicprotocol now respects graceful shutdown.
- Fix logging when
quictransport is used and UDP traffic is proxied. - FIPS compliant cloudflared binaries will now be released as separate artifacts. Recall that these are only for linux and amd64.
- Fixes Github issue #530 where cloudflared 2021.12.0 could not reach origins that were HTTPS and using certain encryption methods forbidden by FIPS compliance (such as Let's Encrypt certificates). To address this fix we have temporarily reverted FIPS compliance from amd64 linux binaries that was recently introduced (or fixed actually as it was never working before).
- Cloudflared binary released for amd64 linux is now FIPS compliant.
- Logging about connectivity to Cloudflare edge now only yields
ERRlevel logging if there are no connections to Cloudflare edge that are active. Otherwise it logsWARNlevel.
- Fixes Github issue #501.
- Fallback from
protocol:quictoprotocol:http2immediately if UDP connectivity isn't available. This could be because of a firewall or egress rule.
- Collect quic transport metrics on RTT, packets and bytes transferred.
- Fix race condition that was writing to the connection after the http2 handler returns.
cloudflaredcan now run withquicas the underlying tunnel transport protocol. To try it, change or add "protocol: quic" to your config.yml file or run cloudflared with the--protocol quicflag. e.g:cloudflared tunnel --protocol quic run <tunnel-name>
- Fixed some generic transport bugs in
quicmode. It's advised to upgrade to at least this version (2021.9.2) when runningcloudflaredwithquicprotocol. cloudflareddocker images will now show version.
- Temporary tunnels (those hosted on trycloudflare.com that do not require a Cloudflare login) now run as Named Tunnels underneath. We recall that these tunnels should not be relied upon for production usage as they come with no guarantee of uptime. Previous cloudflared versions will soon be unable to run legacy temporary tunnels and will require an update (to this version or more recent).
- Because Equinox os shutting down, all cloudflared releases are now present here. Equinox will no longer receive updates.
- Prevents tunnel from accidentally running when only proxy-dns should run.
- If auto protocol transport lookup fails, we now default to a transport instead of not connecting.
- Fixes a http2 transport (the new default for Named Tunnels) to work with unix socket origins.
- Fixes a memory leak in h2mux transport that connects cloudflared to Cloudflare edge.
- Uses new Worker based login helper service to facilitate token exchange in cloudflared flows.
- Fixes Centos-7 builds.
- When creating a DNS record to point a hostname at a tunnel, you can now use --overwrite-dns to overwrite any existing
DNS records with that hostname. This works both when using the CLI to provision DNS, as well as when starting an adhoc
named tunnel, e.g.:
cloudflared tunnel route dns --overwrite-dns foo-tunnel foo.example.comcloudflared tunnel --overwrite-dns --name foo-tunnel --hostname foo.example.com
- Named Tunnels will automatically select the protocol to connect to Cloudflare's edge network.
-
It is now possible to run the same tunnel using more than one
cloudflaredinstance. This is a server-side change and is compatible with any client version that uses Named Tunnels.To get started, visit our developer documentation.
-
cloudflared tunnel ingress validatewill now warn about unused keys in your config file. This is helpful for detecting typos in your config. -
If
cloudflareddetects it is running inside a Linux container, it will limit itself to use only the number of CPUs the pod has been granted, instead of trying to use every CPU available.
- Fixed proxying of websocket requests to avoid possibility of losing initial frames that were sent in the same TCP packet as response headers #345.
proxy-dnsoption now works in conjunction with running a named tunnel #346.
- Reverted 2021.3.5 improvement to use HTTP/2 in a best-effort manner between cloudflared and origin services because it was found to break in some cases.
- HTTP/2 transport is now always chosen if origin server supports it and the service url scheme is HTTPS. This was previously done in a best attempt manner.
- The MacOS binaries were not successfully released in 2021.3.3 and 2021.3.4. This release is aimed at addressing that.
- Tunnel create command, as well as, running ad-hoc tunnels using
cloudflared tunnel -name NAME, will not overwrite existing files when writing tunnel credentials.
- Tunnel create and delete commands no longer use path to credentials from the configuration file.
If you need ot place tunnel credentials file at a specific location, you must use
--credentials-fileflag. - Access ssh-gen creates properly named keys for SSH short lived certs.
- It is now possible to obtain more detailed information about the cloudflared connectors to Cloudflare Edge via
cloudflared tunnel info <name/uuid>. It is possible to sort the output as well as output in different formats, such as:cloudflared tunnel info --sort-by version --invert-sort --output json <name/uuid>. You can obtain more information viacloudflared tunnel info --help.
- Don't look for configuration file in default paths when
--config FILEflag is present aftertunnelsubcommand. - cloudflared access token command now functions correctly with the new token-per-app change from 2021.3.0.
- Cloudflare One Routing specific commands
now show up in the
cloudflared tunnel route --helpoutput. - There is a new ingress type that allows cloudflared to proxy SOCKS5 as a bastion. You can use it with an ingress
rule by adding
service: socks-proxy. Traffic is routed to any destination specified by the SOCKS5 packet but only if allowed by a rule. In the following example we allow proxying to a certain CIDR but explicitly forbid one address within it:
ingress:
- hostname: socks.example.com
service: socks-proxy
originRequest:
ipRules:
- prefix: 192.168.1.8/32
allow: false
- prefix: 192.168.1.0/24
ports: [80, 443]
allow: true
- Nested commands, such as
cloudflared tunnel run, now consider CLI arguments even if they appear earlier on the command. For instance,cloudflared --config config.yaml tunnel runwill now behave the same ascloudflared tunnel --config config.yaml run - Warnings are now shown in the output logs whenever cloudflared is running without the most recent version and
no-autoupdateistrue. - Access tokens are now stored per Access App instead of per request path. This decreases the number of times that the user is required to authenticate with an Access policy redundantly.
- GitHub PR #317 was broken in 2021.2.5 and is now fixed again.
- We introduce Cloudflare One Routing in beta mode. Cloudflare customer can now connect users and private networks with RFC 1918 IP addresses via the Cloudflare edge network. Users running Cloudflare WARP client in the same organization can connect to the services made available by Argo Tunnel IP routes. Please share your feedback in the GitHub issue tracker.
- Reverts the Improvement released in 2021.2.3 for CLI arguments as it introduced a regression where cloudflared failed to read URLs in configuration files.
- cloudflared now logs the reason for failed connections if the error is recoverable.
- Removes db-connect. The Cloudflare Workers product will continue to support db-connect implementations with versions of cloudflared that predate this release and include support for db-connect.
- Introduces support for proxy configurations with websockets in arbitrary TCP connections (#318).
- (reverted) Nested command line argument handling.
- The maximum number of upstream connections is now limited by default which should fix reported issues of cloudflared exhausting CPU usage when faced with connectivity issues.