-
Notifications
You must be signed in to change notification settings - Fork 9.7k
[CF1] 1033 error and Tunnel status codes #25863
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 3 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -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: | ||||||
|
||||||
| 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: | |
| First, [review whether your tunnel is listed as Active](/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors/#tunnel-status) 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, check the following: |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i know this was copied over from the old FAQ, but Step 1 (CNAME record) should be unrelated to the tunnel connection status. Wonder if 1033 actually means Cloudflare was unable to connect to a hostname through the tunnel?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1033 usually means that there is no healthy cloudflared replica to receive this traffic from our edge. If request is actually routed to a cloudflared instance, but it cannot send it further to an application, you will see a cloudflared error page, not Cloudflare edge one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nikitacano @ranbel I amended line to provide further explanation based on this detail.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1033 usually means that there is no healthy cloudflared replica to receive this traffic from our edge. If request is actually routed to a cloudflared instance, but it cannot send it further to an application, you will see a cloudflared error page, not Cloudflare edge one.
In that case, we should delete Step 1 since it wouldn't resolve the 1033 error. The resolution would be the steps described for an "Inactive" or "Down" tunnel (i.e. run the tunnel, check for server-side issues).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like the best thing to do would be to tell the user 1) check the status of your tunnel 2) refer to the status table to find the resolution steps according to the tunnel status.
but this would only make sense if a 1033 means the status has to be "down" or "inactive." Is it always the case in 1033 error situations that a tunnel is down or inactive?
@nikitacano can you provide guidance on how to resolve a 1033 error? does my proposed step 1 and step 2 work, or do you have another suggestion?
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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. | |
| 1. Make sure you have a [DNS record](/cloudflare-one/connections/connect-networks/routing-to-tunnel/dns/) which points the application's hostname 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. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't have to be a CNAME or LB, it can also be published application (which is CNAME under the hood, but customers might not know it).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nikitacano is @ranbel 's proposed copy good to go or would you like to propose another suggestion?
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -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 /> | | ||||||
|
||||||
| | **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 /> | | |
| | **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 /> | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.