Skip to content

Commit 3e590e7

Browse files
deadlypants1973deadlypants1973
authored
[CF1] 1033 error and Tunnel status codes (#25863)
* [CF1] 1033 error and Tunnel status codes * notifications edit * note about status scope * updates
1 parent 14416fb commit 3e590e7

File tree

6 files changed

+44
-23
lines changed

6 files changed

+44
-23
lines changed

‎src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors.mdx‎

Lines changed: 14 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,21 @@ sidebar:
55
order: 2
66
---
77

8-
import { Tabs, TabItem, GlossaryTooltip } from "~/components";
8+
import { Tabs, TabItem, GlossaryTooltip, Render } from "~/components";
99

1010
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/).
1111

12+
## Tunnel status
13+
14+
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:
15+
16+
<Render file="tunnel/tunnel-status" product="cloudflare-one" />
17+
18+
:::note[Tunnel status scope]
19+
20+
The tunnel status only reflects the connection between `cloudflared` and the Cloudflare network. Tunnel status does not indicate whether `cloudflared` can successfully reach your internal services. As a result, a tunnel can appear `Healthy` while users are still unable to connect to an application.
21+
:::
22+
1223
## I see `cloudflared service is already installed`.
1324

1425
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 +63,9 @@ This means the origin is using a certificate that `cloudflared` does not trust.
5263

5364
## I see an error 1033 when attempting to run a tunnel.
5465

55-
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:
56-
57-
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.
58-
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)).
66+
<Render file="tunnel/1033-error" product="cloudflare-one" />
5967

60-
For more information, here is a [comprehensive list](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/) of Cloudflare 1xxx errors.
68+
For more information, refer to the [comprehensive list](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/) of Cloudflare 1xxx errors.
6169

6270
## I see `ERR_TOO_MANY_REDIRECTS` when attempting to connect to an Access self-hosted app.
6371

‎src/content/docs/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx‎

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -267,12 +267,7 @@ To check the status of your tunnel:
267267
4. Go to **Networks** > **Tunnels** and search by your tunnel name.
268268
5. Review that the [Tunnel status](/cloudflare-one/connections/connect-networks/monitor-tunnels/notifications/#available-notifications) says `Active`, and not `Down`, `Degraded`, or `Inactive`.
269269

270-
| Status | Meaning | Recommended Action |
271-
|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
272-
| **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. |
273-
| **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). |
274-
| **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. |
275-
| **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 /> |
270+
<Render file="tunnel/tunnel-status" product="cloudflare-one" />
276271

277272
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.
278273

‎src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1033.mdx‎

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,15 +4,16 @@ title: Error 1033
44
source: null
55
---
66

7-
## Error 1033: Argo Tunnel error
7+
import { Render } from "~/components";
88

9-
This error indicates an issue with resolving an Argo Tunnel.
9+
## Error 1033: Cloudflare Tunnel error
10+
11+
This error indicates an issue with [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/).
1012

1113
### Common cause
1214

13-
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.
15+
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.
1416

1517
### Resolution
1618

17-
- **If you are a visitor to this website**: Please try again in a few minutes.
18-
- **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.
19+
<Render file="tunnel/1033-error" product="cloudflare-one" />

‎src/content/notifications/index.yaml‎

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -511,12 +511,7 @@ entries:
511511
nextSteps: Monitor tunnel health over time and consider deploying [`cloudflared` replicas or load balancers](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/).
512512
otherFilters: None.
513513
additional_information: |-
514-
| <div style="width:75px">Health status</div> | Description |
515-
| ------------- | ------------ |
516-
| Healthy | The tunnel is active and serving traffic through four connections to the Cloudflare global network. |
517-
| Degraded | The tunnel is active and 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.|
518-
| Down | The tunnel cannot serve traffic as it has no connections to the Cloudflare global network.|
519-
| Inactive | This value is reserved for tunnels which have been created, but have never been run.|
514+
Refer to [Tunnel status](/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors/#tunnel-status) to review the list of possible tunnel statuses (`Active`, `Inactive`, `Down` and `Degraded`).
520515
521516
- name: Device connectivity anomaly
522517
audience: Zero Trust customers who want to be notified when Cloudflare detects a spike or drop in the number of devices connected to the WARP client.

‎src/content/partials/cloudflare-one/tunnel/1033-error.mdx‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
{}
3+
4+
---
5+
6+
import { Render } from "~/components";
7+
8+
A `1033` error indicates your tunnel is not connected to Cloudflare's network because Cloudflare's network cannot find a healthy `cloudflared` instance to receive the traffic.
9+
10+
First, review whether your tunnel is listed as `Active` on the [Zero Trust](https://one.dash.cloudflare.com/) dashboard by going to **Networks** > **Tunnels** or run `cloudflared tunnel list`. If the tunnel is not `Active`, review the following and take the action necessary for your tunnel status:
11+
12+
<Render file="tunnel/tunnel-status" product="cloudflare-one" />

‎src/content/partials/cloudflare-one/tunnel/tunnel-status.mdx‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
{}
3+
---
4+
5+
| Status | Meaning | Recommended Action |
6+
|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
7+
| **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. |
8+
| **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). |
9+
| **Down** | The tunnel was previously connected but is currently disconnected because the `cloudflared` process has stopped. | 1. Ensure the `cloudflared` [service](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/as-a-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. |
10+
| **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](/cloudflare-one/connections/connect-networks/monitor-tunnels/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 /> |

0 commit comments

Comments
 (0)