Error 105 ERR_SOCKET_NOT_CONNECTED is a vague and frequent error seen in Google Chrome. Following the error, you will see a message that says “The server’s DNS address could not be resolved”.
Since this is such a common error, there are multiple ways to go about resolving it. We have six proven methods below that have worked for other users. We suggest method 2, which is to flush the socket pool. This is the most common cause of the error.
- 1 What Is Error 105 ERR_SOCKET_NOT_CONNECTED?
- 2 What Causes 105 ERR_SOCKET_NOT_CONNECTED?
- 3 How to Fix 105 ERR_SOCKET_NOT_CONNECTED
- 4 Final Words
What Is Error 105 ERR_SOCKET_NOT_CONNECTED?
Error 105 ERR_SOCKET_NOT_CONNECTED is an error that pops up in Google Chrome. It means that the DNS lookup has failed. The DNS is what’s responsible for translating a website name to the address it holds on the internet. Additionally, it means the socket on the browser is having issues.
What Causes 105 ERR_SOCKET_NOT_CONNECTED?
There are several causes for the error message, but the main cause is due to the sockets on your PC. However, here are some of the other causes for the error message:
- *Pools of sockets in Google Chrome may be corrupt or not properly working.
- *Java installs may be contributing the error
- *The DNS may not be accessible
- *Browser storage and installation files may be corrupt or damaged
- *Third-party plugins
How to Fix 105 ERR_SOCKET_NOT_CONNECTED
Luckily there are multiple ways the 105 ERR_SOCKET_NOT_CONNECTED can be resolved. This includes:
- *Clearing cookies and cache from Chrome
- *Flushing the socket pool
- *Checking Java installs
- *Flush DNS
- *Set Google’s DNS
- *Changing your proxy settings
- *Reinstall Chrome
Before you continue with these methods, ensure you have an open and active internet connection. There shouldn’t be any proxies installed on your PC and you should be using a private network rather than a work or public network.
Alright, if you have that set, let’s continue with the methods below:
Method 1: Clearing Cookies and Cache from Chrome
Whenever you visit a website, the information from the page or anything you add to it is saved, including pictures that are on the website. It saves everything so when you get on the website again, it loads quicker. All of this information can essentially clog your browser and create issues such as the 105 ERR_SOCKET_NOT_CONNECTED error. Luckily you can clear your browser’s cache and cookies very easily. Here’s how to do it:
- *Open your Chrome Browser
- *Click on the three dots in the upper right-hand corner
- *Click on More tools
- *Select Clear browsing data
- *Select all time on the rime range
- *Check Cookies and other page data & Cached images and files as well all other boxes you want to clear out (I don’t suggest Passwords if you don’t remember the passwords for all the websites you have logged into)
- *Click Clear Browsing Data
Once you have done this, restart Chrome and try to access the web again. If this did not work, continue on to the next method.
Method 2: Flushing the Socket Pool
This method almost always works for clearing up the 105 ERR_SOCKET_NOT_CONNECTED error. It’s called “flushing the socket pool” and it empties the plugs from your browser. It will interrupt any website you still have open and you may need to reset some things. Let’s get started:
- *Enter this URL in Chrome chrome://net-internals/
- *Once opened, select Plugs tab in the left pane
- *Click Flush socket pools
- *Restart Chrome and attempt to access the website again
Method 3: Check Java Installs
As mentioned above, several cases reported by Chrome users were because of Java installs. This is nothing to worry about with this issue since it can be easily fixed by installing the most recent version of Java.
- *Navigate to the app manager on your computer
- *Press Win + R and type appwiz.cpl
- *Install the latest version of Java
- *Once done, type Win + R
- *Type Control and press enter
- *Choose the Large icons from the top-right side
- *Select Java 32-bit
- *Select the Java tab
- *Click View
- *Select add to search the directory where your Java installations are
- *Save the changes and exit
- *Restart your computer and try the webpage again
Method 4: Flush DNS
Flushing the DNS can fix a variety of errors including this one. So to do that you need to get to command prompt. Here’s how to perform the whole operation:
- *Click on Start
- *Type CMD
- *Right-click on it and Run as administrator
- *Type the following command once the command prompt opens
- *Press Enter
- *Once some time has passed it will be completed
- *Once done, close the command prompt
- *Run the terminal.app by going to Applications then to Utilities
- *Type sudo killall -HUP mDNSResponder
- *Hit Return
- *Enter your administrator password for the account
- *Hit Return
- *Press Ctrl+Alt+T to launch a terminal window
- *Enter the command sudo /etc/init.d/nscd restart
- *If asked, enter your password
- *To clear the dnsmasq DNS cache, enter sudo /etc/init.d/dnsmasq restart
- *Enter your password again if asked
- *To flush the local BIND DNS cache, enter one of these commands:
- *Sudo /etc/init.d/named restart
- *Sudo ends restart
- *Sudo rndc exec
Method 5: Set Google’s DNS
Setting Google’s DNS as your primary DNS before trying any of the below methods. The DNS is an essential part of any system and it allows it to resolve the names when accessing websites. If your computer can’t get to the DNS server, it won’t connect to the website after you type its address into the browser. Here’s how to fix that:
- *Press Win + R
- *Type Control panel in the box and hit enter
- *Click on Network and Internet
- *Select Network and Sharing Center
- *Click on the network you are connected to present next to Connections
- *Click Properties
- *Click twice on Internet Protocol Version 4 (TCP/IPv4)
- *Select Use the following DNS server addresses
- *Save any information that may be shown in case you need it for later use
- *Enter the following values:
- *Preferred DNS server: 188.8.131.52.
- *Alternate DNS server: 184.108.40.206.
- *Select OK to save changes and exit
- *Restart your computer and try to access the website again
Method 6: Change Your Proxy Settings
Another way you can get rid of the 105 ERR_SOCKET_NOT_CONNECTED error is to use a proxy server if all else fails.
- *Click on the Chrome menu
- *Click Settings
- *Choose Show advanced settings
- *Click on Modify proxy settings
- *Click LAN Settings
- *Uncheck the option Use a proxy server for your local network
- *Close the tab page
- *Try the website again
Method 7: Reinstall Google Chrome
The last step for hopefully fixing the 105 ERR_SOCKET_NOT_CONNECTED error is to reinstall Chrome. Here’s how:
- *Hit the Win + R keys
- *Open Run
- *Enter the command %USERPROFILE%\AppData\Local\Google\Chrome\User Data
- *Select the folder Default
- *Hit the Shift + Delete combo
- *Click Yes upon prompt
- *Open Chrome and click Menu
- *Click Settings
- *Navigate to Advanced
- *Scroll to Restore settings to their original defaults
- *Click on Reset
- *Try the webpage again
We hope that you found one of these methods helpful and that the 105 ERR_SOCKET_NOT_CONNECTED error is gone. As we previously mentioned it’s a very vague error that has many reasons for popping up. It’s common and doesn’t mean there’s anything terribly wrong with your PC.