glad i'm not alone on this one, having the exact same issue and noticed it's tied to only experimental. changing and forcing a different proton version works at the moment but is a work-a-round
Seems to be related to the FSR4 Dll that was leaked and then removed by them
I'm having the same issue. Asahi Linux (macbook pro).
cd ~/.steam/steam/logs
cat content_log.txt
[2026-06-24 08:13:47] CDepotDownloadMgr::BYldRequestDepotManifest(App: 1493710, Depot: 4862111, Manifest: 5497140658785823969, branch: ): Failed to get manifest request code, 'Access Denied'
Closing in favor of https://github.com/ValveSoftware/steam-for-linux/issues/13339.
Compatibility Report
System Information
I confirm:
Symptoms
Proton Experimental cannot complete its own update/manifest check. Steam's content_log.txt shows a repeating, never-succeeding error:
Failed to get manifest request code, 'Access Denied'
App: 1493710, Depot: 4862111, Manifest: 5497140658785823969
This happens on every scheduler cycle. Steam's UI surfaces this as a generic "No internet connection" error — both as a queue download failure and as an instant "An error occurred while launching this game: No internet connection" when launching any game set to use Proton Experimental as its compatibility tool (confirmed with Cyberpunk 2077, AppID 1091500).
Network connectivity is confirmed fully working: verified reachability to current Steam CM servers (via
GetCMListForConnectAPI) and CDN endpoints (Akamai) with curl/netcat, confirmed successful Steam login in connection_log.txt, and confirmed Steam Store/Community pages load normally. This is not a network, DNS, firewall, or ISP issue — it is isolated to this specific depot/manifest request being denied server-side.Running "Verify integrity of game files" on Proton Experimental completes with "0 files failed to validate and will be reacquired" but does not resolve the manifest request failure — the same Access Denied error recurs immediately after.
Workaround: switching the affected game's compatibility tool from Proton Experimental to a stable numbered Proton version (Proton 9.0) resolves the launch failure entirely, confirming the issue is isolated to Proton Experimental's own depot/manifest and not a general compatibility or network problem.
Reproduction
~/.steam/debian-installation/logs/content_log.txt— observe repeatedFailed to get manifest request code, 'Access Denied'for App 1493710, Depot 4862111.