ERR_INTERNET_DISCONNECTED but Wi-Fi Works? Here’s the Fix

If Chrome shows ERR_INTERNET_DISCONNECTED while your Wi-Fi icon says you are connected, the usual cause is not your router. It is something on your own device telling Chrome there is no network at all, most often a VPN that quit badly, a leftover proxy setting, or a security tool blocking Chrome. Start by opening the same page in a second browser. That one test splits the problem in half.

What this error actually means

ERR_INTERNET_DISCONNECTED is net error -106 in Chrome’s network stack. In Chromium’s own error list it is described as “The Internet connection has been lost.” (net_error_list.h)

The important detail is when Chrome gives up. This error fires before Chrome looks up the site’s address and before it opens any connection. Chrome has asked the operating system whether a usable network exists, been told no, and stopped there. It never reached the internet, so it never reached the site.

That is why the most common advice you will find, flushing your DNS cache, usually does nothing here. A DNS flush helps errors that happen during a name lookup. This error happens before the lookup even starts.

Who this applies to

• Google Chrome on Windows, Mac, Linux, ChromeOS, Android, or iPhone
• Any recent Chrome version. This error is not tied to one release
• No Google account or admin rights needed for the first few checks
• Some Windows fixes below need an administrator account

The 60-second test that tells you which fix you need

Do this before you change a single setting. Open a different browser on the same device, such as Edge, Safari, or Firefox, and load any website.

• The other browser also fails. The problem is your device or your network, not Chrome. Go to branch 1 or branch 2.
• The other browser loads fine. The problem is specific to Chrome or to a setting only Chrome is honoring. Go to branch 3 or branch 4.

On a Chromebook you can be more precise. Select the time in the bottom right, then Settings, then About ChromeOS, then Diagnostics, then Connectivity. It tests the Wi-Fi link, DNS, and the path out to the internet separately, so you can see which leg is failing. (Chromebook Help. Requires ChromeOS 90 or later.)

Why this happens: four causes and how to tell them apart

Branch 1: you are on the network but not on the internet

Your device joined the Wi-Fi, so the icon looks healthy, but nothing gets past the router. A captive portal is the classic version of this. Hotel, airport, campus, and cafe networks hold you at a sign-in page until you accept their terms.

Your signal that this is you: every browser and every app fails, and it started the moment you joined a network you do not own. Phones on cellular data work fine.

Branch 2: the network adapter is in a bad state

The adapter is connected in name only. It has no valid address, or it is holding a stale one, so the operating system reports “no usable network” to every app that asks. Waking from sleep and switching between Wi-Fi and Ethernet are common triggers.

Your signal that this is you: everything fails, but other devices on the same Wi-Fi are perfectly fine, and a restart fixes it for a while before it comes back.

Branch 3: a VPN or proxy left a dead route behind

This is the branch most people are actually in when Wi-Fi looks fine. A VPN that crashed or was force-quit can leave its kill switch armed or its virtual adapter half-attached. A proxy entry can also stay behind after a VPN, a work laptop setup, or an extension is removed, pointing Chrome at a server that no longer answers.

Your signal that this is you: another browser works, or the failure began right after a VPN disconnected, updated, or crashed.

Branch 4: security software is blocking Chrome specifically

Firewalls and antivirus suites filter traffic per application. After a Chrome update the executable changes, and a strict rule can start blocking the new one while leaving every other app alone.

Your signal that this is you: only Chrome fails, other browsers are fine, and it started right after a Chrome update or a new security product was installed.

Fixes for each branch

If it is the network (branch 1)

1. Disconnect from the Wi-Fi network and reconnect. On public Wi-Fi this usually forces the sign-in page to appear.
2. If no sign-in page appears, open http://neverssl.com in a new tab. Captive portals cannot intercept an HTTPS page, which is why the portal often never shows up on its own.
3. On your own network, restart the router and wait two full minutes before testing.

If it is the adapter (branch 2)

1. Turn Wi-Fi off and on again from the system tray or status area.
2. Forget the network, then rejoin it and enter the password again.
3. Restart the device. If the error returns after every sleep, your adapter driver or power settings are the likely cause, not Chrome.

Warning: the next step resets Windows networking components and will remove custom network configuration, including static IP and manual DNS entries. Note down anything you have customized first, and skip this on a work or school machine that IT manages.

4. On Windows, open Command Prompt as administrator and run netsh winsock reset, then netsh int ip reset, then restart the PC.

If it is a VPN or proxy (branch 3)

1. Open your VPN app, connect properly, then disconnect using the app’s own button. Force-quitting is what leaves the kill switch armed, and reconnecting is what disarms it cleanly.
2. If the VPN is uninstalled or will not open, remove its network adapter or profile from your system network settings.
3. On Windows, open Settings, go to Network & internet, then Proxy. Turn Automatically detect settings off, and make sure Use a proxy server is off unless your workplace told you to use one. This switch is on by default in Windows 11.
4. On a Mac, open System Settings, then Network, select your active connection, then Details, then Proxies, and confirm nothing is enabled.
5. Test Chrome in a guest profile. If it works there, an extension is setting the proxy, and Chrome will name it at the top of the proxy settings page.

If it is security software (branch 4)

Warning: the first step below turns off protection on your device. Do it only long enough to test, stay off risky sites while it is off, and turn it back on immediately afterwards.

1. Pause your third-party antivirus or firewall for one minute and reload the page.
2. If that fixes it, turn protection back on and instead find Chrome in the product’s application or firewall rules list and allow it.
3. On Windows, also check Windows Defender Firewall and confirm Chrome is allowed on both private and public networks.
4. If Chrome is missing from the rules list entirely, reinstalling Chrome will re-register it.

How this differs from Chrome’s other connection errors

The error text tells you how far Chrome got before it failed, which is the fastest way to narrow down a fix.

If you are seeing one of the DNS errors instead, a host cache clear is worth trying. Go to chrome://net-internals/#dns and select Clear host cache. For ERR_INTERNET_DISCONNECTED, this is not where the problem is.

If none of this works

Be aware that this error is a symptom, not a diagnosis. It reports the end result, that Chrome saw no network, without saying which piece of software caused it. We could not find an official Google acknowledgement of a Chrome bug that produces this error on its own, and there is no published fix or timeline to wait for. If every branch above comes back clean, the cause is almost certainly a local networking component rather than Chrome itself.

At that point, two things are worth doing. Test the same device on a completely different network, such as a phone hotspot. If it works there, the fault is your original network. If it fails everywhere, create a new user account on the device and try Chrome there, which rules out a broken profile or a per-user network setting.

FAQ

Why does my Wi-Fi icon show connected if there is no internet?

The icon reports the link between your device and the router. It says nothing about whether the router can reach the internet, or whether your device has a valid address. Those are separate steps, and any of them can fail while the icon still looks fine.

Will clearing my cache and cookies fix ERR_INTERNET_DISCONNECTED?

Almost never. Cached data is only read after Chrome has decided a network exists. This error means it decided one does not. Clearing browsing data is harmless, but it is not the fix here.

Why does the error only appear in Chrome and not in other browsers?

Because something is scoped to Chrome alone. On Windows, Chrome reads the system proxy settings, so a stale proxy entry can hit Chrome while a browser using its own settings is unaffected. A firewall rule that blocks the Chrome executable behaves the same way.

Can this error be caused by the website itself?

No. Chrome never contacted the site. If one site fails while others load, you are looking at a different error, most likely one from the DNS or connection family in the table above.

Wrapping up

The second-browser test is what saves you time on this error. It splits four causes into two, and it takes less than a minute. If the fault turns out to be Chrome-only, check the proxy setting and your firewall rules before anything else, because those two account for most cases where Wi-Fi genuinely is working.

Related reading

• Fix ERR_NAME_NOT_RESOLVED in Chrome: 7 Working Solutions
• Fix ERR_CONNECTION_RESET in Chrome: Every Working Solution
• Chromebook Keeps Disconnecting from Wi-Fi? Here’s the Fix
• Fix Error Code 7: 0x80072EFD in Google Chrome