WebSocket sessions still die after a cloudflared upgrade, but only through one proxy path.
A Cloudflare Tunnel upgrade restores websockets and one path still drops because an intermediate proxy resets idle HTTP/2 streams at a shorter timer
The tunnel is healthy, but a middle proxy times out upgraded streams earlier than the edge expects.
Scenario
What to check first
- Identify the primary failure signal in the The Tunnel Stayed Up and the Middle Proxy Grew Impatient Before the Conversation Was Done 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
Compare idle timers between edge, tunnel, and middle proxy before rolling back.
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