Some users have reported an ERR_SOCKET_NOT_CONNECTED error for Google Chrome. This is a rather vague error, but it can be caused by several factors such as socket pools, DNS server issues, third-party plugins causing problems, etc.
In this article, we will learn how to get rid of this error on Windows 10 computers.
What causes ERR_SOCKET_NOT_CONNECTED?
- DNS server: The DNS server used by your computer may not be available.
- Socket Pools: The socket pool of your Chrome browser is corrupt or not working properly.
- Java installation: In some cases, installing Java on your computer may also contribute to this error message.
- Browser problems: If all of the above causes are ruled out, only browser problems remain, including memory and installation files.
How do I solve the ERR_SOCKET_NOT_CONNECTED problem?
Change the DNS server
- Right-click the network icon on the taskbar and select Network and Sharing Center.
- Click on the Change card settings option.
- Locate the network connection you are using.
- Right-click on your network connection and select Properties.
- Select the Internet Protocol 4 (TCP/IPv4) option.
- Click the Properties button and in the new window check the Use the following DNS server addresses option.
- Enter 188.8.131.52 and 184.108.40.206 and click OK.
Uninstalling apps from your browser
- Open Chrome and press Alt + F.
- Go to More Tools and click Extensions to search for suspicious extensions or browser toolbars.
- Click the trash can and select Uninstall.
- Restart Google Chrome and press Alt + F again.
- Select Open a specific page or set of pages.
- Click Set Pages to replace the URL if it’s active.
Empty the socket pool
- Open Google Chrome and type chrome://net-internals/ in the address bar.
- Select “Sockets” on the left side.
- Select Empty Socket Pools on the right side.
- Once the process is complete, restart your Chrome browser.
Frequently Asked Questions
ERR_SOCKET_NOT_CONNECTED. This error message means that your browser's socket has a problem. A socket can be thought of as the end point of two-way communication between two programs running on the Internet.
It is possible that the DNS server that your computer uses is not available. Also, your Chrome browser's socket pool is either corrupt or not working properly.
- Change your DNS server.
- Remove applications from your browser.
- Empty the socket pool.