ERR_SOCKET_NOT_CONNECTED -15
Net error -15
The socket is not connected.
Also searched as: net::ERR_SOCKET_NOT_CONNECTED, error -15
What it means
A page fails with ERR_SOCKET_NOT_CONNECTED because Chrome tried to use a network socket that was no longer connected. It often happens after sleep/resume or network changes, and a reset of Chrome's socket pools usually clears it.
Applies to: Chrome, Edge, Brave, Opera, Vivaldi
How to fix ERR_SOCKET_NOT_CONNECTED
- Open 'chrome://net-internals/#sockets' and click 'Flush socket pools', then reload
- Clear the host cache at 'chrome://net-internals/#dns'
- Restart Chrome completely (check the system tray so it is not still running in the background)
- Flush DNS with 'ipconfig /flushdns' and, if needed, run 'netsh winsock reset' as administrator
- Change DNS to a public resolver (1.1.1.1 or 8.8.8.8) if errors keep coming back
- Disable VPN and proxy software to test
Why it happens
Chromium reuses pooled connections. If the underlying socket was closed by the OS, the network changed, or a filter driver dropped it, Chrome may attempt to use it and fail with this code.
FAQ
Does flushing socket pools delete my data?
No. It only closes idle network connections; Chrome reopens them as needed.
Related errors
Source: Chromium net_error_list.h · fixes written and reviewed by the editors (see our editorial policy)
Last updated: