Google Chrome ERR_SOCKET_NOT_CONNECTED: How to Fix It

Easy 10-30 minutes Medium Severity Verified June 2026
Error Code
ERR_SOCKET_NOT_CONNECTED
Brand
Google Chrome
Product Type
browser
Severity
Medium
DIY Difficulty
Easy
Estimated Fix Time
10-30 minutes
The ERR_SOCKET_NOT_CONNECTED error in Google Chrome means the browser tried to send or receive data through a network socket, but that connection was already closed or was never properly established. This typically happens when Chrome's internal socket pool gets corrupted, a proxy or VPN interferes with the connection, or your network stack has an underlying issue. The good news is that this error is almost always fixable through software and settings changes — no hardware repair is needed.
Ad

Tools You'll Need

How to Fix Error Code ERR_SOCKET_NOT_CONNECTED

  1. Reload the Page and Restart Chrome

  2. Flush Chrome's Socket Pools

  3. Clear Chrome's DNS Cache

  4. Disable Proxy Settings and VPN

  5. Flush the System DNS and Reset the Network Stack

    Running network reset commands requires administrator rights. On Windows, right-click Command Prompt and choose 'Run as administrator' before typing these commands.
  6. Disable Chrome Extensions

  7. Clear Chrome Browsing Data

  8. Change Your DNS Server

  9. Update or Reinstall Google Chrome

    Before reinstalling Chrome, note your saved passwords or ensure they are synced to your Google account so you do not lose them.
  10. Check Your Firewall and Antivirus Software

    Only disable security software briefly for testing. Re-enable it immediately after confirming whether it is the cause.
Ad

When to Call a Professional

If you have completed all steps and ERR_SOCKET_NOT_CONNECTED continues across multiple networks (home Wi-Fi, mobile hotspot, and ethernet), the issue may be related to a deeper OS network stack corruption, a failing network adapter driver, or a managed corporate firewall policy. Contact your IT department if this is a work-managed device, reach out to your Internet Service Provider if the problem affects all browsers, or consult a computer technician if the network stack reset commands produce errors or do not resolve the problem.

Frequently Asked Questions

What does ERR_SOCKET_NOT_CONNECTED mean in Chrome?
It means Chrome attempted to use a network socket connection to communicate with a server, but that socket was already closed, dropped, or never successfully opened. It is usually caused by a stale socket pool inside Chrome, a proxy or VPN misconfiguration, DNS resolution failure, or a network stack issue on your computer.
Why does ERR_SOCKET_NOT_CONNECTED only appear on certain websites?
When the error affects only specific sites, it usually points to a DNS caching problem for that particular domain, a server-side issue with that site, or an extension or proxy rule targeting certain URLs. Try flushing Chrome's DNS cache at chrome://net-internals/#dns and disabling extensions to isolate the cause.
How do I flush socket pools in Chrome?
Type 'chrome://net-internals/#sockets' into Chrome's address bar and press Enter. On the page that appears, click 'Flush socket pools' and then 'Close idle sockets'. This clears all stale open and pending socket connections Chrome is holding internally and is one of the fastest fixes for this error.
Can a VPN cause ERR_SOCKET_NOT_CONNECTED in Chrome?
Yes. VPNs route your traffic through a different network path, and if the VPN tunnel drops, times out, or has a routing conflict, Chrome's socket connections can fail. Disable your VPN temporarily and reload the page. If it works without the VPN, try reconnecting to a different VPN server or contact your VPN provider's support.
Does reinstalling Chrome fix ERR_SOCKET_NOT_CONNECTED?
It can, especially if Chrome's profile or installation files have become corrupted. Uninstall Chrome through your system's application manager, restart your computer, then download and install the latest version from google.com/chrome. Make sure your bookmarks and passwords are backed up to your Google account before uninstalling.