Xbox Cloud Gaming — Persistent Stream Connection Failure

Xbox Cloud Gaming — Persistent Stream Connection Failure


Summary

Xbox Cloud Gaming streams intermittently fail to connect. The Xbox logo appears, a brief clip of audio plays (timing is inconsistent — sometimes under a second, sometimes a few seconds), and the session hangs for 15–30 seconds before closing without any error. This has been reproducible across multiple titles, multiple browsers, and multiple networks over roughly a week of testing.

Environment

• OS: Fedora Linux (Workstation)
• GPU: NVIDIA GeForce RTX 5070, driver 615.71.09
• Browsers tested: Google Chrome (stable) and Firefox — same failure on both
• Networks tested: Home network (AT&T fiber, BGW320-500 gateway, wired ethernet) and a phone hotspot on a separate carrier — same failure on both
• Titles tested: Control, Control: Ultimate Edition, A Plague Tale: Requiem — failure is not consistently tied to any one title

Console error (Chrome/Firefox DevTools)

WebRtcStream: Connect. GameStreamError: Failed to connect to game stream. at ue.connectAsync (web-rtc-stream...) at async ht.doConnectAsync at async ht.connectAsync at async xl.connectToSession (game-stream...) at async xl.cloudConnect

WebRTC diagnostics (chrome://webrtc-internals)

• iceState=connected, dtlsState=connected, candidate-pair state=succeeded — signaling and the underlying transport connect successfully
• Candidate pairing is direct host-to-host UDP to a Microsoft/Azure endpoint (no TURN relay involved)
• On the video track specifically: packetsReceived and retransmittedPacketsReceived climb together, but keyFramesDecoded stays at zero — video packets are being sent and lost, NACK-based retransmission partially compensates, but not enough to assemble a decodable frame. The audio track is unaffected by the same loss due to its much smaller bandwidth footprint.

What's been ruled out

• GPU/driver issues (Vulkan, hardware decode, VRAM/thermal headroom all confirmed healthy)
• Browser-specific cause (identical failure on Chrome and Firefox)
• Home router NAT (confirmed via IP Passthrough, bypassing NAT entirely — failure persisted)
• MTU/fragmentation (tested at MTU 1400 — failure persisted)
• Local network quality (Waveform bufferbloat test: Grade A, +17ms latency under load, ~940 Mbps down/up; only "Low Latency Gaming" flagged as degraded)
• Local bandwidth contention (confirmed no other devices active on the network during a failure)
• SDP/codec negotiation mismatch (negotiated SDP is consistent across every session — standard H.264 profiles + Opus, no anomalies)
• A specific network path (same failure reproduced on both home fiber and an unrelated cellular hotspot)

Known related reports
This is a previously documented failure signature, not unique to this setup:

• A 2024 GitHub issue (ungoogled-chromium) reports the identical console error verbatim
• A better-xcloud GitHub discussion describes the same Xbox-logo/black-screen/GameStreamError symptom, with webrtc-internals showing a stuck ICE connection

Conclusion
Given the failure reproduces across browsers, networks, and ISPs, while consistently showing real packet loss on the video track after a successful connection handshake, this points to an issue in Xbox Cloud Gaming's server-side session/media path rather than anything in the local client, network, or hardware.

submitted by /u/Some_Procedure_4430
[link] [comments]