ERR_SOCKET_NOT_CONNECTED in Chrome — What It Means & How to Fix It

Chrome's ERR_SOCKET_NOT_CONNECTED error means a reused connection socket became invalid. Here's how to fix it.

Frequently asked questions

What does ERR_SOCKET_NOT_CONNECTED mean?
Chrome failed to create or use a network socket to connect to the server. This often indicates a problem with Chrome's internal socket pool — connections that Chrome kept open in the background have all gone stale.
How do I fix ERR_SOCKET_NOT_CONNECTED quickly?
Go to chrome://net-internals/#sockets and click 'Flush socket pools', then reload the page. This is the most reliable quick fix for this specific error.
Will this error go away on its own?
Sometimes yes — if it was triggered by a temporary network hiccup, a simple reload or browser restart resolves it. If it persists, flushing Chrome's socket pools (see above) is the right fix.
Upload your screenshot for a specific explanation →