[CF1] 1033 error and Tunnel status codes

deadlypants1973 · deadlypants1973 · commit bb49186ae7cf · 2025-10-15T19:56:58.000+01:00
diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors.mdx
@@ -5,10 +5,16 @@ sidebar:
   order: 2
 ---
 
-import { Tabs, TabItem, GlossaryTooltip } from "~/components";
+import { Tabs, TabItem, GlossaryTooltip, Render } from "~/components";
 
 This section covers the most common errors you might encounter when connecting resources with Cloudflare Tunnel. If you do not see your issue listed below, refer to the [troubleshooting FAQ](/cloudflare-one/faq/troubleshooting/), view your [Tunnel logs](/cloudflare-one/connections/connect-networks/monitor-tunnels/logs/), or [contact Cloudflare Support](/support/contacting-cloudflare-support/).
 
+## 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:
+
+<Render file="tunnel/tunnel-status" product="cloudflare-one" />
+
 ## I see `cloudflared service is already installed`.
 
 If you see this error when installing a remotely-managed tunnel, ensure that no other `cloudflared` instances are running as a service on this machine. Only a single instance of `cloudflared` may run as a service on any given machine. Instead, we recommend adding additional routes to your existing tunnel. Alternatively, you can run `sudo cloudflared service uninstall` to uninstall `cloudflared`.
@@ -52,12 +58,9 @@ This means the origin is using a certificate that `cloudflared` does not trust.
 
 ## I see an error 1033 when attempting to run a tunnel.
 
-An error 1033 indicates your tunnel is not connected to Cloudflare's edge. First, run `cloudflared tunnel list` to see whether your tunnel is listed as active. If it isn't, check the following:
-
-1. Make sure you correctly routed traffic to your tunnel (step 5 in the [Tunnel guide](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/create-local-tunnel/#5-start-routing-traffic)) by assigning a CNAME record to point traffic to your tunnel. Alternatively, check [this guide](/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb/) to route traffic to your tunnel using load balancers.
-2. Make sure you run your tunnel (step 6 in the [Tunnel guide](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/create-local-tunnel/#6-run-the-tunnel)).
+<Render file="tunnel/1033-error" product="cloudflare-one" />
 
-For more information, here is a [comprehensive list](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/) of Cloudflare 1xxx errors.
+For more information, refer to the [comprehensive list](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/) of Cloudflare 1xxx errors.
 
 ## I see `ERR_TOO_MANY_REDIRECTS` when attempting to connect to an Access self-hosted app.
 
diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx
@@ -267,12 +267,7 @@ To check the status of your tunnel:
 4. Go to **Networks** > **Tunnels** and search by your tunnel name.
 5. Review that the [Tunnel status](/cloudflare-one/connections/connect-networks/monitor-tunnels/notifications/#available-notifications) says `Active`, and not `Down`, `Degraded`, or `Inactive`.
 
-| Status    | Meaning                                                                                                                                                           | Recommended Action                                                                                                                                                                                                                                                                                            |
-|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **Healthy**   | The tunnel is active and serving traffic through four connections to the Cloudflare global network.                                    | No action is required. Your tunnel is running correctly.                                                                                                                                                                                                                                                       |
-| **Inactive**  | The tunnel has been created (via the API or dashboard) but the `cloudflared` connector has never been run to establish a connection.                          | Run the tunnel as a service (recommended) or use the `cloudflared tunnel run` command on your origin server to connect the tunnel to Cloudflare. Refer to [substep 6 of step 1 in the Create a Tunnel dashboard guide](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/#1-create-a-tunnel) or step 4 in the [Create a Tunnel API guide](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/#1-create-a-tunnel).                           |
-| **Down**      | The tunnel was previously connected but is currently disconnected because the `cloudflared` process has stopped.                                            | 1. Ensure the `cloudflared` service or process is actively running on your server. <br /> 2. Check for server-side issues, such as the machine being powered off, an application crash, or recent network changes.                                                                                                |
-| **Degraded**  | The `cloudflared` connector is running and the tunnel is serving traffic, but at least one individual connection has failed. Further degradation in [tunnel availability](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/) could risk the tunnel going down and failing to serve traffic.               | 1. Review your `cloudflared` logs for connection failures or error messages. <br /> 2. Investigate local network and firewall rules to ensure they are not blocking connections to the [Cloudflare Tunnel IPs and ports](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-with-firewall/). <br />                                                                        |
+<Render file="tunnel/tunnel-status" product="cloudflare-one" />
 
 For detailed steps on troubleshooting, refer to the [Troubleshooting Tunnel documentation](/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/). Review the [Tunnel with Firewall documentation](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-with-firewall/#test-connectivity) to ensure your network is correctly configured to allow `cloudflared` connections.
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1033.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1033.mdx
@@ -4,15 +4,16 @@ title: Error 1033
 source: null
 ---
 
-## Error 1033: Argo Tunnel error
+import { Render } from "~/components";
 
-This error indicates an issue with resolving an Argo Tunnel.
+## Error 1033: Cloudflare Tunnel error
+
+This error indicates an issue with [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/).
 
 ### Common cause
 
-You have requested a page on a website (`tunnel.example.com`) that is on the Cloudflare network. The host (`tunnel.example.com`) is configured as an Argo Tunnel, and Cloudflare is currently unable to resolve it.
+You have requested a page on a website (`tunnel.example.com`) that is on the Cloudflare network. The host (`tunnel.example.com`) is configured with Cloudflare Tunnel, and Cloudflare is currently unable to resolve it.
 
 ### Resolution
 
-- **If you are a visitor to this website**: Please try again in a few minutes.
-- **If you are the owner of this website**: Ensure that _cloudflared_ is running and can reach the network. You may wish to enable [load balancing](/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb) for your tunnel.
+<Render file="tunnel/1033-error" product="cloudflare-one" />
diff --git a/src/content/partials/cloudflare-one/tunnel/1033-error.mdx b/src/content/partials/cloudflare-one/tunnel/1033-error.mdx
@@ -0,0 +1,11 @@
+---
+{}
+
+---
+
+A `1033` error indicates your tunnel is not connected to Cloudflare's network.
+
+First, run `cloudflared tunnel list` to [review whether your tunnel is listed as Active](/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors/#tunnel-status). If it is not, check the following:
+
+1. Make sure you correctly routed traffic to your tunnel (step 5 in the [Tunnel guide](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/create-local-tunnel/#5-start-routing-traffic)) by assigning a CNAME record to point traffic to your tunnel. Alternatively, check [this guide](/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb/) to route traffic to your tunnel using load balancers.
+2. Make sure you run your tunnel (step 6 in the [Tunnel guide](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/create-local-tunnel/#6-run-the-tunnel)).
diff --git a/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx b/src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx
@@ -0,0 +1,10 @@
+---
+{}
+---
+
+| Status    | Meaning                                                                                                                                                           | Recommended Action                                                                                                                                                                                                                                                                                            |
+|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Healthy**   | The tunnel is active and serving traffic through four connections to the Cloudflare global network.                                    | No action is required. Your tunnel is running correctly.                                                                                                                                                                                                                                                       |
+| **Inactive**  | The tunnel has been created (via the API or dashboard) but the `cloudflared` connector has never been run to establish a connection.                          | Run the tunnel as a service (recommended) or use the `cloudflared tunnel run` command on your origin server to connect the tunnel to Cloudflare. Refer to [substep 6 of step 1 in the Create a Tunnel dashboard guide](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/#1-create-a-tunnel) or step 4 in the [Create a Tunnel API guide](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/#1-create-a-tunnel).                           |
+| **Down**      | The tunnel was previously connected but is currently disconnected because the `cloudflared` process has stopped.                                            | 1. Ensure the `cloudflared` service or process is actively running on your server. <br /> 2. Check for server-side issues, such as the machine being powered off, an application crash, or recent network changes.                                                                                                |
+| **Degraded**  | The `cloudflared` connector is running and the tunnel is serving traffic, but at least one individual connection has failed. Further degradation in [tunnel availability](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/) could risk the tunnel going down and failing to serve traffic.               | 1. Review your `cloudflared` logs for connection failures or error messages. <br /> 2. Investigate local network and firewall rules to ensure they are not blocking connections to the [Cloudflare Tunnel IPs and ports](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-with-firewall/). <br />                                                                        |
