Updating UI copy for /cf1/connections/connect-networks/

Oxyjun · Oxyjun · commit 4f70bbc3e0d2 · 2025-10-27T15:22:59.000Z
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cloudflared-parameters/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cloudflared-parameters/index.mdx
@@ -142,8 +142,8 @@ On Windows, Cloudflare Tunnel installs itself as a system service using the Regi
 
 To configure how `cloudflared` sends requests to your [published applications](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/):
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels**.
-2. Choose a tunnel and select **Configure**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**.
+2. Choose a tunnel and select **Edit**.
 3. Select the **Published application routes** tab.
 4. Choose an application and select **Edit**.
 5. Under **Additional application settings**, modify one or more [origin configuration parameters](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cloudflared-parameters/origin-parameters/).
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx
@@ -15,7 +15,7 @@ To get the token for a remotely-managed tunnel:
 
 <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**.
 2. Select a `cloudflared` tunnel and select **Edit**.
 3. Copy the `cloudflared` installation command.
 4. Paste the installation command into any text editor. The token value is of the form `eyJhIjoiNWFiNGU5Z...`
@@ -61,7 +61,7 @@ To rotate a tunnel token:
 
 <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**.
 2. Select a `cloudflared` tunnel and select **Edit**.
 3. Select **Refresh token**.
 4. Copy the `cloudflared` installation command for your operating system. This command contains the new token.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/ansible.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/ansible.mdx
@@ -299,7 +299,7 @@ Once you have created the configuration files, you can deploy them through Terra
    terraform apply
    ```
 
-It may take several minutes for the GCP instance and tunnel to come online. You can view your new tunnel in [Zero Trust](https://one.dash.cloudflare.com) under **Networks** > **Tunnels**.
+It may take several minutes for the GCP instance and tunnel to come online. You can view your new tunnel in [Cloudflare One](https://one.dash.cloudflare.com) under **Networks** > **Connectors** > **Cloudflare Tunnels**.
 
 ## 7. Test the connection
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/aws.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/aws.mdx
@@ -98,8 +98,9 @@ EOF
 
 [Private network routes](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/) allow users to connect to your virtual private cloud (VPC) using the WARP client. To add a private network route for your Cloudflare Tunnel:
 
-1. In the **CIDR** tab, enter the **Private IPv4 address** of your AWS instance (for example, `172.31.19.0`). You can expand the IP range later if necessary.
-2. In your [Split Tunnel configuration](/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels/#add-a-route), make sure the private IP is routing through WARP. For example, if you are using Split Tunnels in **Exclude** mode, delete `172.16.0.0/12`. We recommend re-adding the IPs that are not explicitly used by your AWS instance.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Networks** > **Routes**.
+2. In the **CIDR** tab, enter the **Private IPv4 address** of your AWS instance (for example, `172.31.19.0`). You can expand the IP range later if necessary.
+3. In your [Split Tunnel configuration](/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels/#add-a-route), make sure the private IP is routing through WARP. For example, if you are using Split Tunnels in **Exclude** mode, delete `172.16.0.0/12`. We recommend re-adding the IPs that are not explicitly used by your AWS instance.
 
         To determine which IP addresses to re-add, subtract your AWS instance IPs from `172.16.0.0/12`:
 
@@ -113,7 +114,7 @@ EOF
 
         Add the results back to your Split Tunnel Exclude mode list.
 
-3.  To test on a user device:
+4.  To test on a user device:
     1. [Log in to the WARP client](/cloudflare-one/team-and-resources/devices/warp/deployment/manual-deployment/).
     2. Open a terminal window and connect to the service using its private IP:
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/azure.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/azure.mdx
@@ -13,8 +13,8 @@ We will walk through how to initialize a service on a Linux VM in Azure, and rou
 
 ## Prerequisites
 
-- In [Zero Trust](https://one.dash.cloudflare.com/), create a Cloudflare Zero Trust account.
-- [Enroll an end-user device](/cloudflare-one/team-and-resources/devices/warp/deployment/manual-deployment/) into your Cloudflare Zero Trust account.
+- In [Cloudflare One](https://one.dash.cloudflare.com/), create a Cloudflare One account.
+- [Enroll an end-user device](/cloudflare-one/team-and-resources/devices/warp/deployment/manual-deployment/) into your Cloudflare One account.
 
 ## Create your environment
 
@@ -113,4 +113,4 @@ systemctl start cloudflared
 systemctl status cloudflared
 ```
 
-Next, visit Zero Trust and ensure your new tunnel shows as **active**. Optionally, begin creating [Access policies](/cloudflare-one/access-controls/policies/) to secure your private resources.
+Next, visit Cloudflare One and ensure your new tunnel shows as **active**. Optionally, begin creating [Access policies](/cloudflare-one/access-controls/policies/) to secure your private resources.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/kubernetes.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/kubernetes.mdx
@@ -147,9 +147,9 @@ A pod represents an instance of a running process in the cluster. In this exampl
 
 To create a Cloudflare Tunnel:
 
-1. Open a new browser tab and log in to [Zero Trust](https://one.dash.cloudflare.com).
+1. Open a new browser tab and log in to [Cloudflare One](https://one.dash.cloudflare.com).
 
-2. Go to **Networks** > **Tunnels**.
+2. Go to **Networks** > **Connectors** > **Cloudflare Tunnels**.
 
 3. Select **Create a tunnel**.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx
@@ -439,7 +439,7 @@ If you would prefer to manually install the tunnel, refer to [Install and run th
 
 <Render file="terraform/deploy-terraform" product="cloudflare-one" />
 
-It may take several minutes for the GCP instance and tunnel to come online. You can view your new tunnel, Access application, and Access policy in [Zero Trust](https://one.dash.cloudflare.com). The new DNS records are available in the [Cloudflare dashboard](/dns/manage-dns-records/how-to/create-dns-records/).
+It may take several minutes for the GCP instance and tunnel to come online. You can view your new tunnel, Access application, and Access policy in [Cloudflare One](https://one.dash.cloudflare.com). The new DNS records are available in the [Cloudflare dashboard](/dns/manage-dns-records/how-to/create-dns-records/).
 
 :::note[Remove Terraform resources]
 
@@ -448,9 +448,9 @@ If you need to roll back the configuration, run `terraform destroy` to delete ev
 
 ## 7. Test the connection
 
-1. In **Networks** > **Tunnels**, verify that your tunnel is active.
+1. In **Networks** > **Connectors** > **Cloudflare Tunnels**, verify that your tunnel is active.
 
-2. In **Access** > **Applications**, verify that your Cloudflare email is allowed by the Access policy.
+2. In **Access controls** > **Applications**, verify that your Cloudflare email is allowed by the Access policy.
 
 3. From any device, open a browser and go to `http_app.<CLOUDFLARE_ZONE>` (for example, `http_app.example.com`).
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/update-cloudflared.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/update-cloudflared.mdx
@@ -94,8 +94,8 @@ sudo systemctl restart cloudflared.service
 
 **If you created a remotely-managed tunnel using the [dashboard](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/):**
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels**.
-2. Select your tunnel and select **Configure**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**.
+2. Select your tunnel and select **Edit**.
 3. Select **Docker** and copy the installation command shown in the dashboard. The copied command will contain your token.
 4. Paste this command into a terminal window.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel.mdx
@@ -7,7 +7,7 @@ sidebar:
 
 import { Render } from "~/components";
 
-Follow this step-by-step guide to create your first [remotely-managed tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/tunnel-useful-terms/#remotely-managed-tunnel) using Zero Trust.
+Follow this step-by-step guide to create your first [remotely-managed tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/tunnel-useful-terms/#remotely-managed-tunnel) using Cloudflare One.
 
 ## 1. Create a tunnel
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/tunnel-useful-terms.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/tunnel-useful-terms.mdx
@@ -29,7 +29,7 @@ You can create and configure a tunnel once and run that tunnel through multiple,
 
 ## Remotely-managed tunnel
 
-A remotely-managed tunnel is a [tunnel](#tunnel) that was created in [Zero Trust](https://one.dash.cloudflare.com/) under **Networks** > **Tunnels**. Tunnel configuration is stored in Cloudflare, which allows you to manage the tunnel from the dashboard or using the [API](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/subresources/configurations/methods/get/).
+A remotely-managed tunnel is a [tunnel](#tunnel) that was created in [Cloudflare One](https://one.dash.cloudflare.com/) under **Networks** > **Tunnels**. Tunnel configuration is stored in Cloudflare, which allows you to manage the tunnel from the dashboard or using the [API](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/subresources/configurations/methods/get/).
 
 ## Locally-managed tunnel
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs.mdx
@@ -30,7 +30,7 @@ You can view real-time logs for a Cloudflare Tunnel via the dashboard or from an
 
 Dashboard log streams are only available for remotely-managed tunnels. To view logs from the dashboard:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels** and select a remotely-managed tunnel.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels** and select a remotely-managed tunnel.
 2. In the sidebar, select the **Connector ID** for the `cloudflared` instance you want to view.
 3. Select **Begin log stream**.
 
@@ -40,7 +40,7 @@ The `cloudflared` daemon can stream logs from any tunnel in your account to the
 
 #### View logs
 
-1. On your local machine, authenticate `cloudflared` to your Zero Trust account:
+1. On your local machine, authenticate `cloudflared` to your Cloudflare One account:
 
    ```sh
    cloudflared tunnel login
@@ -77,7 +77,7 @@ cloudflared tail --level debug <UUID>
 
 If you are running multiple `cloudflared` instances for the same tunnel (also known as [replicas](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/)), you must specify an individual instance to stream logs from:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels** and select your tunnel.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels** and select your tunnel.
 2. Find the **Connector ID** for the `cloudflared` instance you want to view.
 3. Specify the Connector ID in `cloudflared tail`:
    ```sh
@@ -86,5 +86,5 @@ If you are running multiple `cloudflared` instances for the same tunnel (also kn
 
 ### Performance considerations
 
-- The logging session will only be held open for one hour. All logging systems introduce some level of performance overhead, and this limit helps prevent longterm impact to your tunnel's end-to-end latencies.
+- The logging session will only be held open for one hour. All logging systems introduce some level of performance overhead, and this limit helps prevent long term impact to your tunnel's end-to-end latencies.
 - When streaming logs for a high throughput tunnel, Cloudflare intentionally prioritizes service stability over log delivery. To reduce the number of dropped logs, try [requesting fewer logs](#filter-logs). To ensure that you are seeing all logs, [view logs on the server](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/#view-logs-on-the-server) instead of streaming the logs remotely.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/private-dns.mdx
@@ -54,7 +54,7 @@ Both `dig` commands will fail if the WARP client is disabled on your end user's
 
 Use the following troubleshooting strategies if you are running into issues while configuring private DNS with Cloudflare Tunnel.
 
-- Ensure that `cloudflared` is connected to Cloudflare by visiting **Networks** > **Tunnels** in Zero Trust.
+- Ensure that `cloudflared` is connected to Cloudflare by visiting **Networks** > **Connectors** > **Cloudflare Tunnels** in Cloudflare One.
 
 - Ensure that `cloudflared` is running with the `quic` protocol (search for `Initial protocol quic` in its logs).
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-connector/site-to-site.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-connector/site-to-site.mdx
@@ -40,8 +40,8 @@ In this example, we will create a WARP Connector for subnet `10.0.0.0/24` and in
 
 ## 3. Route traffic between WARP Connector and Cloudflare
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Networks** > **Routes**.
-2. Select **Create route**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Networks** > **Routes**.
+2. Select **Add a route**.
 3. In **CIDR**, enter the private IPv4 address range that you wish to route through this WARP Connector (for example, `10.0.0.0/24`). WARP Connector does not currently support IPv6 routes.
    :::note
    If you do not already have a private network range, you can choose a subnet from one of these [pre-defined CIDRs](https://datatracker.ietf.org/doc/html/rfc1918#section-3).
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-to-warp.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-to-warp.mdx
@@ -25,13 +25,13 @@ This guide covers how to:
 
 - [Install the Cloudflare WARP client](/cloudflare-one/team-and-resources/devices/warp/deployment/) on your devices.
 - [Define device enrollment permissions](/cloudflare-one/team-and-resources/devices/warp/deployment/device-enrollment/).
-- [Enroll your devices](/cloudflare-one/team-and-resources/devices/warp/deployment/manual-deployment/) in your Zero Trust organization.​​
+- [Enroll your devices](/cloudflare-one/team-and-resources/devices/warp/deployment/manual-deployment/) in your Zero Trust organization.
 
 ## Enable WARP-to-WARP
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Network**.
-2. Enable **Proxy**.
-3. Enable **Warp-to-Warp**. This allows Cloudflare to route traffic to the <GlossaryTooltip term="CGNAT IP">CGNAT IP</GlossaryTooltip> space.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Management**.
+2. Select **Peer to peer connectivity**.
+3. Enable **Allow WARP to WARP connection**. This allows Cloudflare to route traffic to the <GlossaryTooltip term="CGNAT IP">CGNAT IP</GlossaryTooltip> space.
 4. In your [Split Tunnel configuration](/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels/), ensure that traffic to `100.96.0.0/12` is going through WARP:
 
 - If using **Exclude** mode, delete `100.64.0.0/10` from the list and re-add `100.64.0.0/11` and `100.112.0.0/12`.
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx
@@ -32,7 +32,7 @@ To create a load balancer for Cloudflare Tunnel published applications:
 7. Enter a descriptive name for the pool. For example, if you are configuring one pool per tunnel, the pool name can match your tunnel name.
 8. To add a tunnel endpoint to the pool, configure the following fields:
 			- **Endpoint Name**: Name of the server that is running the application
-			- **Endpoint Address**: `<UUID>.cfargotunnel.com`, where `<UUID>` is replaced by your Tunnel ID. You can find the **Tunnel ID** in [Zero Trust](https://one.dash.cloudflare.com) under **Networks** > **Tunnels**.
+			- **Endpoint Address**: `<UUID>.cfargotunnel.com`, where `<UUID>` is replaced by your Tunnel ID. You can find the **Tunnel ID** in [Cloudflare One](https://one.dash.cloudflare.com) under **Networks** > **Connectors** > **Cloudflare Tunnels**.
 			- **Header value**: Hostname of your published application route (such as `app.example.com`). To find the hostname value, open your Cloudflare Tunnel configuration and go to the **Published application routes** tab.
 			- **Weight**: Assign a [weight](/load-balancing/understand-basics/traffic-steering/origin-level-steering/#weights) to the endpoint. If you only have one endpoint, enter `1`.
 	:::note
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx
@@ -11,7 +11,7 @@ This section covers the most common errors you might encounter when connecting r
 
 ## Tunnel status
 
-You can check your tunnel’s connection status either from the Zero Trust dashboard (by going to **Networks** > **Tunnels**) or by running the `cloudflared tunnel list` command. Each tunnel displays a status that reflects its current connection state:
+You can check your tunnel's connection status either from Cloudflare One (by going to **Networks** > **Connectors** > **Cloudflare Tunnels**) or by running the `cloudflared tunnel list` command. Each tunnel displays a status that reflects its current connection state:
 
 <Render file="tunnel/tunnel-status" product="cloudflare-one" />
 
@@ -104,7 +104,7 @@ There are a few different possible root causes behind the `websocket: bad handsh
 
 ## My tunnel randomly disconnects.
 
-Long-lived connections initiated through the Cloudflare Zero Trust platform, such as SSH sessions, can last up to eight hours. However, disruptions along the service path may result in more frequent disconnects. Often, these disconnects are caused by regularly scheduled maintenance events such as data center, server, or service updates and restarts. If you believe these events are not the cause of disconnects in your environment, collect the relevant [WARP logs](/cloudflare-one/team-and-resources/devices/warp/troubleshooting/warp-logs/) and [Tunnel logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) and contact Support.
+Long-lived connections initiated through Cloudflare One, such as SSH sessions, can last up to eight hours. However, disruptions along the service path may result in more frequent disconnects. Often, these disconnects are caused by regularly scheduled maintenance events such as data center, server, or service updates and restarts. If you believe these events are not the cause of disconnects in your environment, collect the relevant [WARP logs](/cloudflare-one/team-and-resources/devices/warp/troubleshooting/warp-logs/) and [Tunnel logs](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) and contact Support.
 
 ## Tunnel connections fail with SSL error.
 
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access.mdx
