Jul 22, 2018  Available Sockets From the left top corner menu select sockets option. Available Sockets Now you will get a page where is option ‘Flush Socket Pools’ click on it. It will clean all records. Line two begins with the name of the network application (Google Chrome), separated by a period from the process ID (which in the example is 7523). Line three shows one network socket listed for the application.

If you get host connection errors, a quick fix to try is flushing the DNS cache. Has its own internal DNS cache which relies on more than one Domain Name Server so does not clear the Google Chrome's DNS cache as well. A different method is needed.

Fortunately, Chrome has built-in tools for flushing the DNS cache and Sockets. Here's how to use them. Open Chrome and type in the address bar (omnibox), the following: chrome://net-internals/#dns Simply copy/paste the line above and press Enter. Notice the active and expired entries and all the IP addresses that were stored in the DNS cache. Press the Clear host cache button. Notice the active and expired entries numbers changed to 0.

Let's move on to Sockets. Switch to chrome://net-internals/#sockets as shown below. Press Close idle sockets and Flush socket pools. Method 2 Alternatively, you could flush the DNS and Sockets by using the drop down menu on top right, available across all features under chrome://net-internals/. Method 3 The DNS cache is also cleared if you clear the browsing history from the Advanced Settings in Chrome. This will flush the DNS cache but won't flush the Sockets as well. You'll need method 1 and 2 above for that.

Note that by using this method your history of visited sites will be deleted as well. Open Clear browsing data. A fast way to do this is to press Ctrl+Shift+Del. Or use the classic navigation path: Menu > More tools > Clear browsing data. Check Browsing history and choose the interval you need. If you started experiencing problems recently, you can choose a smaller time period such as 'past day' or 'past week'.

Press Clear browsing data. See the picture below for clarifications on these steps. Using method 1 and 2 from above you'll be able to flush the DNS cache and Sockets in Chrome. Method 3 only clears the DNS cache. Leave a comment below and share with us your reasons for flushing the DNS cache and/or Sockets in Chrome. Bonus: Have a look at.

The error seems to occur when multiple tabs to the same site are open and one tab is awaiting the completion of a task. The other tab is not allowed to do what it needs until the previous tab completes its task. The error 'can result. Try another browser, or even the same one with a single tab to see if it occurs. This may rule out the server.

If it does, then you will know the issue is one the browser side. I did some research on the error message and this seems to be an issue that could also be within your browser.

Are you using Chrome by chance? Have you tried another browser or device?

The error seems to occur when multiple tabs to the same site are open and one tab is awaiting the completion of a task. The other tab is not allowed to do what it needs until the previous tab completes its task. The error 'can result. Try another browser, or even the same one with a single tab to see if it occurs. This may rule out the server. If it does, then you will know the issue is one the browser side. I did some research on the error message and this seems to be an issue that could also be within your browser.