cloudflared-mirror/CHANGES.md

Experimental: This is a new format for release notes. The format and availability is subject to change.

2021.3.3

Improvements

• Tunnel create command, as well as, running ad-hoc tunnels using cloudflared tunnel -name NAME, will not overwrite existing files when writing tunnel credentials.

Bug Fixes

• 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-file flag.
• Access ssh-gen creates properly named keys for SSH short lived certs.

2021.3.2

New Features

• 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 via cloudflared tunnel info --help.

Bug Fixes

• Don't look for configuration file in default paths when --config FILE flag is present after tunnel subcommand.
• cloudflared access token command now functions correctly with the new token-per-app change from 2021.3.0.

2021.3.0

New Features

• Cloudflare One Routing specific commands now show up in the cloudflared tunnel route --help output.
• 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

Improvements

• 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 run will now behave the same as cloudflared tunnel --config config.yaml run
• Warnings are now shown in the output logs whenever cloudflared is running without the most recent version and no-autoupdate is true.
• 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.

Bug Fixes

• GitHub PR #317 was broken in 2021.2.5 and is now fixed again.

2021.2.5

New Features

• 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.

2021.2.4

Bug Fixes

• 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.

2021.2.3

Backward Incompatible Changes

• 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.

New Features

• Introduces support for proxy configurations with websockets in arbitrary TCP connections (#318).

Improvements

• (reverted) Nested command line argument handling.

Bug Fixes

• 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.