On screen: Failed to load web page (unknown error) — Error Code: -130
This error is produced locally. It does not appear because the service is down, so the fixes below are worth working through in order.
This is not a Steam platform code. It comes from the Chromium browser embedded in the Steam client, with the sign inverted: Steam's -130 is Chromium's ERR_PROXY_CONNECTION_FAILED.
Chromium's description: could not create a connection to the proxy server. Something on your machine is routing the client's browser through a proxy that is not answering.
Which means the rest of Steam is very likely working. Your library opens, your games launch, and a part of the client that happens to be a web browser cannot load a page.
Check your system proxy settings. If a proxy is configured and you did not configure it, something installed it — a VPN client, a security product or a so-called optimiser. Turning it off and retrying is the whole test.
Steam's client embeds a Chromium browser, and these numbered codes are Chromium's own network errors with the sign flipped. We verified each one against Chromium's error list rather than guessing. That is why the on-screen message is the same unhelpful line for all of them while the causes are completely different — and why most of them mean Steam is working fine. Valve publishes no article for this code. Worth knowing: Valve publishes no status page of its own. The link in their own support article now redirects to a sales chart. That gap is why we measure Steam ourselves, by probing its public endpoints every five minutes.
This is not a Steam platform code. It comes from the Chromium browser embedded in the Steam client, with the sign inverted: Steam's -130 is Chromium's ERR_PROXY_CONNECTION_FAILED.
This error is produced locally. It does not appear because the service is down, so the fixes below are worth working through in order.
Start with: Turn off the system proxy. Including any automatic configuration script. On Windows this is in Settings under Network, Proxy.