Error 105 err socket not connected in Chrome: Fix

Error 105 (err_socket_not_connected) in Google Chrome means the browser could not establish a network connection to the website you tried to visit, usually because of a temporary network glitch, a misconfigured proxy, or a firewall/antivirus blocking the connection. The fix is straightforward: restart your router and computer, then reset Chrome’s network settings and clear its cache; if that fails, check your proxy settings and firewall rules. Below is a complete guide to resolving this error on Windows, macOS, and Android.

What Causes Error 105 in Chrome

Chrome displays err_socket_not_connected when the underlying socket (the endpoint of a network connection) fails to connect to the server. This is not a problem with the website itself in most cases; it’s a local issue on your device or network. Common triggers include:

• Temporary network hiccups – your Wi-Fi or Ethernet connection dropped for a moment, or the router needs a restart.
• Proxy or VPN interference – a misconfigured proxy, a VPN that disconnected abruptly, or a browser extension that manages connections can cause the socket to fail.
• Firewall or antivirus blocking – security software sometimes mistakes Chrome’s connection attempts for malicious activity and blocks them.
• Corrupted Chrome cache or cookies – stale data can interfere with establishing a new connection.
• Outdated network drivers – especially on Windows, outdated or corrupted network drivers can cause socket errors.
• DNS issues – the domain name may not resolve correctly, preventing the socket from connecting to the right IP address.

Quick Fixes to Try First

Before diving into deeper troubleshooting, try these simple steps, as they resolve the majority of cases:

1. Restart your router and modem – unplug them for 30 seconds, plug them back in, and wait for the lights to stabilize.
2. Restart your computer or phone – a fresh boot clears temporary network states.
3. Check if other websites load – if only one site fails, the problem is likely with that site, not your network.
4. Disable your VPN or proxy temporarily – if you use one, turn it off and try again.
5. Try incognito mode – press Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac) to open an incognito window. If the site loads there, an extension or cached data is the culprit.

Reset Chrome’s Network Settings

If the quick fixes don’t work, Chrome’s internal network settings might be corrupted. Resetting them is safe and doesn’t affect your bookmarks or passwords.

1. Open Chrome and type chrome://net-internals in the address bar, then press Enter.
2. In the left sidebar, click Sockets.
3. Click the Flush socket pools button. This clears all existing socket connections.
4. Go to DNS in the left sidebar and click Clear host cache.
5. Restart Chrome and try the website again.

You can also reset Chrome’s flags by going to chrome://flags and clicking Reset all at the top right, but this is rarely necessary.

Clear Cache and Cookies

Corrupted cache files can cause connection errors. Here’s how to clear them without losing your saved passwords:

1. Click the three-dot menu (⋮) in the top-right corner of Chrome.
2. Go to More tools → Clear browsing data.
3. Set the time range to All time.
4. Check Cookies and other site data and Cached images and files.
5. Click Clear data.
6. Restart Chrome and try again.

If the error persists, you can also try disabling all extensions temporarily by going to chrome://extensions and toggling them off, then re-enabling them one by one to find the culprit.

Check Proxy and Firewall Settings

A misconfigured proxy is a common cause of error 105. Here’s how to check and fix it on Windows and macOS:

Windows

1. Open Settings → Network & Internet → Proxy.
2. Under Manual proxy setup, make sure the toggle is Off unless you actually use a proxy.
3. If you do use a proxy, ensure the address and port are correct.
4. Also, check your firewall (Windows Defender Firewall) to ensure Chrome is allowed through. Go to Allow an app through the firewall and make sure Google Chrome is checked for both Private and Public networks.

macOS

1. Open System Settings → Network.
2. Select your active network (Wi-Fi or Ethernet) and click Details.
3. Click Proxies and ensure no proxy is enabled unless you need one.
4. Check your firewall settings under System Settings → Network → Firewall and ensure Chrome is allowed to accept incoming connections.

Update Network Drivers and Chrome

Outdated network drivers can cause socket errors, especially after a Windows update. Here’s what to do:

• Windows: Open Device Manager (right-click the Start button → Device Manager), expand Network adapters, right-click your adapter, and select Update driver → Search automatically for drivers. If that doesn’t find anything, visit your computer manufacturer’s website for the latest driver.
• macOS: Network drivers are updated via system updates. Go to System Settings → General → Software Update and install any pending updates.
• Chrome: Click the three-dot menu → Help → About Google Chrome. Chrome will automatically check for and install updates. Relaunch the browser after updating.

Frequently Asked Questions

Does error 105 mean my internet is down?

Not necessarily. Error 105 is specific to Chrome and indicates a problem with the socket connection, which can happen even when your internet is working fine for other apps. It’s often a temporary glitch or a Chrome-specific issue.

Can a VPN cause error 105?

Yes, VPNs can cause error 105 if the VPN connection drops or if the VPN server is unreachable. Try disconnecting your VPN and reloading the page. If the error disappears, the VPN was the cause.

Why does error 105 only happen on one website?

If only one website fails, the problem is likely on that website’s server, not your network. Check if the site is down for everyone using a service like downforeveryoneorjustme.com, or try accessing it from a different device or network.

Will clearing my cache delete my passwords?

No, clearing cache and cookies will not delete your saved passwords, but it will log you out of most websites. Your passwords are stored separately in Chrome’s password manager and will remain intact.

Is there a command-line fix for error 105?

You can try flushing your DNS cache from the command line. On Windows, open Command Prompt as administrator and run ipconfig /flushdns. On macOS, run sudo dscacheutil -flushcache in Terminal. This often helps resolve DNS-related socket errors.

Should I reinstall Chrome to fix error 105?

Reinstalling Chrome is a last resort, but it can help if the browser’s files are corrupted. Before doing that, try resetting Chrome’s settings to default by going to chrome://settings/reset and clicking Restore settings to their original defaults. This is less drastic than a full reinstall and often works.

Related

• Restore iPhone from Backup: iCloud & iTunes Steps
• Join Celestial Discord for Drops & Giveaways
• Spell Check Not Working in Google Docs? Fix It