Migrate legacy tunnels

Originally, a Cloudflare Tunnel connection corresponded to a DNS record in your account. Requests to that hostname hit Cloudflare’s network first and our edge sends those requests over the tunnel to your origin. However, fitting an outbound-only connection into a reverse proxy creates some ergonomic and stability hurdles. The original Cloudflare Tunnel architecture attempted to both manage DNS records and create connections. When connections became disrupted, Tunnel would recreate the entire deployment. Additionally, Argo Tunnel connections could not be treated like regular origin servers in Cloudflare’s control plane and had to be managed directly from the server-side software.

Today, Cloudflare Tunnel’s architecture distinguishes between the persistent objects (DNS records, cloudflared) and the ephemeral objects (the connections). To do that, it assigns permanent names and UUIDs to tunnels, which makes them more stable and easier to use. Since the name and UUID for a tunnel do not change, your DNS record never needs to be cleaned up or recreated when Cloudflare Tunnel restarts. In the event of a restart, the enrolled instance of cloudflared connects back to that UUID address.

Check for legacy tunnels

To check if you still have legacy tunnels:

1. Log into the Cloudflare dashboard ↗ and select a zone. Legacy Tunnels are associated with a zone and not by account.
2. Go to Traffic > Cloudflare Tunnel.

If nothing appears, this indicates there are no legacy tunnels associated with the zone. If legacy tunnels appear, follow the migration instructions below.

Note

Named tunnels will only appear in Zero Trust ↗ under Networks > Tunnels.

Migrate legacy tunnels

To migrate your legacy tunnels to the named tunnels architecture:

1. Download the latest version of cloudflared.

2. Obtain a new origin certificate by running cloudflared login. While named tunnels are scoped to an account, for legacy reasons the login page requires selecting a zone.

3. Create a tunnel.

   cloudflared tunnel create <TUNNEL-NAME>

4. Route traffic to your tunnel to create routes that your tunnel will serve.

   • If your legacy tunnel was serving tunnel.example.com, run this command to configure your named tunnel to also serve tunnel.example.com. For more information, refer to the DNS Record routing section.

     cloudflared tunnel route dns <TUNNEL-NAME> tunnel.example.com

   • If you used to run your legacy tunnel with the --lb-pool flag, run this command to set up your named tunnel as a load balancer origin. For more information, refer to the Load Balancers routing section.

     cloudflared tunnel route lb <TUNNEL-NAME> <LOAD-BALANCER-NAME> <LOAD-BALANCER-POOL>

5. Next, create a configuration file with ingress rules. The ingress rules describe how to dispatch requests to your origins based on hostname and path. For example, if in the past you used to run cloudflared tunnel --hostname tunnel.example.com --url https://localhost:3000, you should add an equivalent ingress rule to your configuration file:

   ingress:
     - hostname: tunnel.example.com
       service: https://localhost:3000
     - service: http_status:404
   # Note that the last rule is the catch-all rule and is required.

6. Run your tunnel.

Make sure everything works

Once your migration is done, validate your new named tunnel:

1. Make sure the resource behind the tunnel is accessible.
2. Run cloudflared tunnel info <NAME-or-UUID> to confirm that the named tunnel exists.