[Tunnel] Add a hint for workers + websocket error #21076
Conversation
|
Hey @cicku , thank you for the PR. Is there context attached to this? Where did it come from? |
|
From personal experience. |
...tent/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors.mdx
Outdated
Show resolved
Hide resolved
…roubleshoot-tunnels/common-errors.mdx Co-authored-by: Kate Tungusova <[email protected]>
|
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryEnhanced documentation for troubleshooting tunnels by adding a new hint regarding Workers routes and websocket errors.
Modified Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add |
| @@ -92,6 +92,8 @@ There are a few different possible root causes behind the `websocket: bad handsh | |||
|
|
|||
| - Your SSH or RDP Access application has the [Binding Cookie](/cloudflare-one/identity/authorization-cookie/#binding-cookie) enabled. To disable the cookie, go to **Access** > **Applications** and edit the application settings. | |||
|
|
|||
| - One or more [Workers routes](/workers/configuration/routing/routes/) are overlapping with the tunnel hostname, and the Workers do not properly handle the traffic. To resolve, check if the Workers routes or the Worker code can be adjusted accordingly. | |||
There was a problem hiding this comment.
| - One or more [Workers routes](/workers/configuration/routing/routes/) are overlapping with the tunnel hostname, and the Workers do not properly handle the traffic. To resolve, check if the Workers routes or the Worker code can be adjusted accordingly. | |
| - One or more [Workers routes](/workers/configuration/routing/routes/) are overlapping with the tunnel hostname, and the Workers do not properly handle the traffic. To resolve, you could either exclude your tunnel from the Worker route by not defining a route that includes the tunnel's hostname or update your Worker to only handle specific paths and forward all other requests to the origin, for example, by using `return fetch(req)`. |
Documentation checklist