net::ERR_INTERNET_DISCONNECTED in Chrome showing offline network errors, common causes, and fixes for restoring internet access.

A Chrome tab showing net::ERR_INTERNET_DISCONNECTED never reached a server. Chromium logs it as error -106, and it fires before any DNS lookup or connection attempt.

The fault sits between your device and the open web. A dropped link, a dead router feed, a hotel sign-in page or a VPN kill switch can all trigger it.

What net::ERR_INTERNET_DISCONNECTED Means: Chromium Error -106

The net:: prefix marks the raw form of the code. You see it in the DevTools console and in app logs. The browser page shows a plainer line, such as “No internet” or “You are offline”.

Chromium lists the code as -106 in net_error_list.h. Before sending anything, Chrome asks the operating system whether a working route exists. The answer came back no, so Chrome stopped.

No packet left the machine. So the code tells you nothing about the site you tried to open.

Why Chrome Says No Internet When Wi-Fi Shows Connected

The Wi-Fi icon tracks one hop: your device to the router. It can’t see whether the router lost its own upstream feed.

Captive portals on hotel and airport networks, covered by RFC 8910, hold every request at a sign-in page. A VPN kill switch blocks all traffic once the tunnel drops. The icon stays green in both cases.

How Error -106 Differs From ERR_NAME_NOT_RESOLVED and Similar Codes

ERR_INTERNET_DISCONNECTED is the only code in this group raised before Chrome picks a destination. The rest fail later in the request.

CodeWhat happenedWho fixes it
ERR_INTERNET_DISCONNECTEDNo route exists, so Chrome tried nothingYou: Wi-Fi, portal sign-in or VPN
ERR_ADDRESS_UNREACHABLEA link exists, but no path leads to that addressYour routing, sometimes an old DNS entry
ERR_CONNECTION_REFUSEDThe host was found and declinedSite owner or firewall admin
ERR_NAME_NOT_RESOLVEDWeb access works, but the domain returned no addressDNS provider or the site’s records

A DNS failure calls for a different fix. The guide to clearing err_name_not_resolved in Chrome walks through cache flushes and resolver changes.

If a server accepts the connection and then sends nothing, Chrome reports net::err_empty_response instead.

Form resubmission screens like the err_cache_miss warning come from Chrome’s local storage and don’t involve the network link.

7 Common Causes of net::ERR_INTERNET_DISCONNECTED

CauseClueRepair
Link is goneWi-Fi off, loose cable, airplane mode onReconnect and retest
Router lost its feedWi-Fi connected, no device loads pagesReboot router, check ISP light
Public Wi-Fi sign-inHotel, cafe or airport network you never logged intoLoad an http:// page
VPN kill switchStarted when the tunnel droppedQuit the VPN app fully
Adapter or driver glitchOne PC only, often after sleepReset adapter or reboot
Stale proxyProxy set for a network you leftRemove it
Security app or firewallChrome fails, other apps connectPause it for a test

How to Fix net::ERR_INTERNET_DISCONNECTED in 9 Checks

Go in order. The first two checks show where the fault sits, which cuts the rest short.

1. Try a Second Device on the Same Wi-Fi

If a phone or laptop loads pages, the problem is your machine. If nothing loads on any device, jump to the router check.

2. Ping a Bare IP Address to Rule Out DNS

ping -c 2 1.1.1.1
ping: sendto: Network is unreachable

ping -c 2 example.com

If 1.1.1.1 fails, nothing leaves the machine and DNS isn’t to blame. If only example.com fails, look at DNS.

On Linux, finding your assigned IP address with ip a shows whether the adapter got a lease at all.

3. Toggle Airplane Mode or Reset the Adapter

This drops stale routes and DHCP leases. It clears most single-device cases, especially after a laptop wakes from sleep.

4. Restart the Router and Read the WAN Light

Unplug it for 30 seconds. An amber or red internet light usually points to the ISP.

If the lights are unclear, the 192.168.1.1 router login page shows the WAN status directly.

5. Open an http:// Page on Hotel or Cafe Wi-Fi

HTTPS requests fail quietly behind a captive portal. A plain http:// address lets the portal redirect you to its sign-in page.

curl -I http://neverssl.com

A 302 redirect to an unfamiliar host means a sign-in page is waiting.

6. Can a VPN Cause ERR_INTERNET_DISCONNECTED? Quit It Fully

Yes. A kill switch blocks all traffic when the tunnel falls. A half-closed client can keep those block rules live, so exit the app from the system tray, not just its window.

7. Remove a Proxy Left From Another Network

A proxy set for an office keeps pointing at a server you can’t reach from home. On Windows, open Settings, then Network & internet, then Proxy. On macOS, check the Proxies tab in your Wi-Fi details.

8. Pause Security Software and Extensions

Chrome failing while other apps connect points to a per-app firewall rule. Pause the suite briefly and reload.

Suites that scan HTTPS traffic also trigger certificate authority errors, so one pause can reveal both problems. Test extensions one at a time after that.

9. Reset the Network Stack From the Command Line

SystemCommands
Windows (admin prompt)netsh winsock reset, netsh int ip reset, ipconfig /release && ipconfig /renew
macOSsudo ifconfig en0 down && sudo ifconfig en0 up
Linuxsudo ip link set wlan0 down && sudo ip link set wlan0 up

Linux users can also clear old addresses first. The ip address man page covers the flush options.

net::ERR_INTERNET_DISCONNECTED in DevTools, Playwright and Electron

Developers often hit this code with a working connection. The Offline preset in Chrome DevTools network throttling raises it on every request. Switch it back to No throttling and reload.

Playwright throws the same error when a test calls context.setOffline(true), or when a CI runner blocks outbound traffic. Mocking external calls with page.route() keeps those tests stable.

Electron apps run on Chromium’s network stack, so desktop tools built on it log the code too. Other Chromium browsers behave the same way, including Edge and Brave on Linux.

What Site Owners See When Visitors Report Error -106

Nothing. The request never reached your server, so your access logs stay empty.

Ask the visitor whether other sites open. If none do, the fault is on their end.

External monitoring gives you proof of uptime. Pulsetic, for example, checks a site from multiple regions every 30 seconds and sends alerts by email, SMS, voice call, Slack, Discord, Telegram or webhook. Pages that show an offline notice instead of a blank screen also cut down on confused reports.

FAQs

What does net::ERR_INTERNET_DISCONNECTED mean?

Chrome found no working network route, so it sent no request. Chromium lists it as error -106. The cause sits on your device or local network, not on the website.

How do I fix ERR_INTERNET_DISCONNECTED on Windows 10?

Toggle airplane mode and restart the router. Then run netsh winsock reset, netsh int ip reset and ipconfig /renew from an admin prompt. Remove old proxies and quit any VPN fully.

Can antivirus software cause ERR_INTERNET_DISCONNECTED?

Yes. Firewalls and security suites filter traffic per app, and a strict rule can block Chrome while other apps still connect. Pause the software briefly to confirm.

Reddit threads suggest reinstalling Chrome for error -106. Does that work?

Rarely. Error -106 comes from the network layer, so a fresh Chrome install fails on the same connection. Test a second device and ping 1.1.1.1 before following reinstall advice from Reddit.

What should a Reddit help post about ERR_INTERNET_DISCONNECTED include?

List your OS, whether other devices load pages, the result of ping 1.1.1.1, and any VPN, proxy or security app in use. Reddit helpers can then pinpoint the cause faster.

Willie has over 15 years of experience in Linux system administration and DevOps. After managing infrastructure for startups and enterprises alike, he founded Command Linux to share the practical knowledge he wished he had when starting out. He oversees content strategy and contributes guides on server management, automation, and security.