WebSocket apps fail only on one routed hostname behind Cloudflare Tunnel after origin rewrite rules were added.
A Cloudflare Tunnel stays up and WebSocket requests still fail because one origin path strips the Connection upgrade header after an internal rewrite
The tunnel is healthy, but a rewrite rule removes the upgrade context before the request reaches the origin.
Scenario
What to check first
- Identify the primary failure signal in the The Tunnel Stayed Open and the Upgrade Request Lost Its Secret Handshake While Passing Through the Hallway scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Inspect rewrite and header preservation before blaming the tunnel connector.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field