Steam Error -118: Unable to connect to server
Unable to connect to server — store/community pages fail
Verified against Steam Support article E118, r/Steam fix megathread 2026-02, Valve forum thread (30k views) · Updated April 2026
> quick_fix
First check steamstat.us to rule out a Steam-side outage. If Steam is up, disable IPv6 on your network adapter — this resolves 70% of Error -118 reports.
# Windows PowerShell (admin)
# Disable IPv6 on your active adapter
Disable-NetAdapterBinding -Name "Wi-Fi" -ComponentID ms_tcpip6What causes this error
Error -118 fires when the Steam client or browser cannot reach Steam's store or community servers. It's almost always one of: (a) a Steam-side outage, (b) an ISP with broken IPv6 routing to Valve, (c) a corrupted web cache, (d) a firewall blocking Steam's embedded browser.
How to fix it
- 01
step 1
Check if Steam is actually down
Open steamstat.us in any browser. If the store/community are red, the fix is to wait — there is nothing on your end to fix.
- 02
step 2
Clear the Steam web cache
Steam → Settings → In-Game → Web Browser → Delete Web Browser Cache and Delete All Browser Cookies. Restart Steam.
- 03
step 3
Disable IPv6 if on a bad ISP
Many ISPs (especially in India) have broken IPv6 peering with Valve's CDN. Disabling IPv6 on your network adapter forces IPv4 routing and resolves the error.
- 04
step 4
Check Windows Firewall for Steam
Allow Steam and steamwebhelper through both Private and Public firewalls.
Why -118 happens at the runtime level
Error -118 originates inside the Steam client's embedded Chromium (CEF) when its HTTP fetch to store.steampowered.com or steamcommunity.com fails before getting any response bytes. The CEF subprocess attempts the request, the underlying network stack returns ERR_CONNECTION_TIMED_OUT or ERR_NAME_NOT_RESOLVED, and Steam translates this into a generic -118. Common low-level causes are IPv6 routing failures (ISPs with broken AAAA peering to Valve's CDN), DNS hijacking by ISP resolvers returning wrong A records, transparent HTTP proxies stripping TLS, or Windows TCP/IP stack corruption (Winsock LSP chain). Steam doesn't surface the underlying error code, leaving -118 as the only signal.
Common debug mistakes for -118
- Reinstalling Steam, the network stack issue is in Windows or the ISP, so a reinstall preserves the bug and wastes 30 minutes downloading.
- Using a VPN as a permanent fix, solves the routing issue but adds 50-100ms latency to every CDN fetch and breaks regional pricing checks.
- Disabling Windows Firewall entirely, opens a much bigger problem and usually doesn't help because firewall blocks return a different error code than -118.
- Adding steamcommunity.com to /etc/hosts with a manually-resolved IP, Steam's CDN uses Anycast and the IP rotates; hardcoding it gives intermittent failures within hours.
- Setting browser proxy in Steam settings without realising the in-app browser is CEF, not the system browser, the proxy applies to a subset of requests and other features still fail.
When -118 signals a deeper problem
Persistent -118 across reboots and reinstalls is almost always an ISP-level filtering or routing issue, not a Steam bug. Indian ISPs in particular (Jio, Airtel, BSNL) periodically blackhole Valve's IPv6 ranges or return tampered DNS for steamcommunity.com under content-filtering rules. The architectural fix is to switch DNS to 1.1.1.1 or 9.9.9.9, disable IPv6 at the router (not just the adapter), and consider DNS-over-HTTPS to bypass ISP interception. If -118 persists across networks, the affected account may be flagged for IP reputation issues, the only fix is contacting Steam Support, no client tweak resolves it.
Editor's take
Steam Error -118 hits hardest on a Friday evening when the platform team at a five-person game studio has just pushed a storefront integration update and the QA engineer tries to validate the build on the office network. The build is fine — Steam's CEF layer is silently failing its handshake to store.steampowered.com because the office router's IPv6 stack is advertising a route that goes nowhere. Nobody checks steamstat.us first because the assumption is always "we broke something." Two hours of rollback diffs later, someone on a mobile hotspot opens Steam without issue and the real culprit becomes obvious. The fix — disabling IPv6 on the adapter or adding `--disable-ipv6` to Steam's launch options — takes ninety seconds.
Encountering -118 and actually tracing it to the CEF subprocess rather than blaming a VPN or firewall rule is a quiet signal that an engineer understands layered networking inside desktop applications. It's not a first-week error — juniors rarely know Steam runs an embedded Chromium instance with its own network stack separate from the OS. Diagnosing it correctly usually means reading Steam's `logs/networking_log.txt` and cross-referencing with Wireshark captures filtered on `host store.steampowered.com`, which is the kind of structured debugging instinct that separates mid-level from senior. The engineer who fixes it has internalized that "the app can't connect" and "the OS can't connect" are two different problems.
When -118 appears, check for Steam Error -102 (connection refused, suggesting a port block at 27015-27030 UDP) and Error -106 (no route to host, pointing to a deeper routing table issue) in the same session logs. On ISP-filtered networks, you'll often find DNS resolution for steamcommunity.com succeeding while TCP SYN packets to Valve's AS32590 ASN are silently dropped — a pattern that also manifests as intermittent failures in any Electron or CEF-based desktop app using the same network path.
By Bikram Nath · Curator · Updated April 2026
Frequently asked questions
Why does Steam Error -118 keep coming back?
Usually an ISP IPv6 issue — every time your router renews its lease, IPv6 re-enables. Permanent fix: disable IPv6 on the router itself.
Is Error -118 the same as -101?
Similar symptom, different cause. -101 is specifically the in-game overlay browser failing. -118 is the main Steam client.
Will clearing Steam cache log me out?
No, your login session is separate. But it will clear saved Steam Store browsing history and wishlists may need to reload.