Skip to content

Commit 8f55919

Browse files
authored
Apply suggestion from @ranbel
1 parent e729567 commit 8f55919

File tree

1 file changed

+1
-1
lines changed
  • src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels

1 file changed

+1
-1
lines changed

src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ This means the origin is using a certificate that `cloudflared` does not trust.
6767

6868
For more information, refer to the [comprehensive list](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/) of Cloudflare 1xxx errors.
6969

70-
## I see a 502 Bad Gateway error when connecting to a tunnel route.
70+
## I see a 502 Bad Gateway error when connecting to a tunnel published application route.
7171

7272
A `502 Bad Gateway` error on a tunnel route means the tunnel itself is connected to the Cloudflare network, but `cloudflared` cannot reach the origin service defined in your ingress rule. Unlike [error 1033](#i-see-an-error-1033-when-attempting-to-run-a-tunnel), which indicates the tunnel is not connected to Cloudflare, a 502 error indicates the problem is between `cloudflared` and your local service.
7373

0 commit comments

Comments
 (0)