How to Fix ERR_NETWORK_CHANGED
What ERR_NETWORK_CHANGED means
Every page load in Chrome is tied to the network connection it started on. ERR_NETWORK_CHANGED appears when that connection changes halfway through: you moved from one Wi-Fi network to another, your laptop woke up and rejoined a different network, a VPN connected or dropped, or your router handed your device a new IP address. Rather than mixing pieces of a page from two different connections, Chrome stops the load and shows this error.
The key point is that a working connection usually still exists — it is just not the one the page started on. That is why a simple reload fixes this error so often: the reload starts fresh on the current connection. If reloads keep failing, something is changing the connection again and again — a VPN auto-switching servers, a flaky Wi-Fi adapter dropping and reconnecting, or a router renewing IP addresses too aggressively — and the fixes below track down which one it is.
Common causes
- Switched networks mid-load: moving between Wi-Fi networks, or from Wi-Fi to mobile data, while a page was still loading.
- VPN connected, disconnected, or switched servers: every VPN change reroutes all traffic, which Chrome reads as a network change.
- Router renewed your IP address: a DHCP lease renewal or a router restart gives the device a new address mid-session.
- Proxy or extension toggled the connection: a proxy setting or a VPN browser extension changing state reroutes the browser's traffic.
- Flaky adapter or driver: a Wi-Fi adapter dropping and reconnecting on its own, or the connection flipping between IPv4 and IPv6, makes Chrome see constant changes.
How to fix ERR_NETWORK_CHANGED — step by step
Work through these fixes in order. Most cases are resolved by step 1, 2, or 3.
- Reload the page and give the connection a moment to settle. ERR_NETWORK_CHANGED often appears for just a second or two, while your device finishes moving from one network to another, so the simplest fix is also the most common one. Press F5 or Ctrl+R to reload the page, and if the error is still there, wait ten seconds and reload again. If you just switched Wi-Fi networks, connected to a VPN, or woke the laptop from sleep, the first load fails because it started on the old connection, and the reload starts fresh on the new one. Do not keep hammering reload in a loop: two or three tries are enough to tell whether the problem is a one-off switch or something stuck.
- Disconnect from the network and reconnect to it. If reloads keep failing, force the device to drop the old connection completely and start a clean one. On Windows, click the network icon in the taskbar, disconnect from your Wi-Fi network, wait ten seconds, and reconnect; on a Mac, open System Settings, then Wi-Fi, turn Wi-Fi off, wait ten seconds, and turn it back on. For a wired connection, unplug the Ethernet cable for ten seconds and plug it back in. Then load the page again. This clears the stale route Chrome was holding and gives your device a fresh IP address on the current network, which resolves the error in most cases where the network changed but the old connection lingered.
- Turn off your VPN, proxy, and network extensions. A VPN that connects, disconnects, or switches servers mid-load changes your network path in exactly the way this error reports, and so does a proxy setting or a VPN browser extension toggling itself. Disconnect your VPN completely and close its app before reloading the page; on Windows, also go to Settings, then Network & internet, then Proxy, and make sure Use a proxy server is turned off. In Chrome, type chrome://extensions and toggle off any VPN, proxy, or network-related extensions, then reload. If the page loads with everything off, reconnect the VPN to a single stable server and leave it there rather than letting it auto-switch.
- Restart your router and modem and renew your IP address. If the error appears on every device or keeps coming back, the network itself is flapping: the router may be handing out new IP addresses or dropping briefly. Unplug your router and modem from power for a full 30 seconds, plug the modem back in first, wait until its lights go solid, then plug in the router and wait two to three minutes. On Windows, open Terminal as administrator and run ipconfig /release followed by ipconfig /renew and ipconfig /flushdns; on a Mac, renew the DHCP lease from the Wi-Fi details page. Then reload the page. If your phone's hotspot loads the site fine, the home router or its link to your ISP is the problem.
- Reset the network stack and disable IPv6. When the connection keeps switching between IPv4 and IPv6, or between two adapters, Chrome sees a network change on nearly every load. On Windows, right-click the Start button, choose Terminal (Admin), and run netsh winsock reset followed by netsh int ip reset, then restart the computer. If the error persists, disable IPv6 as a test: press Win+R, type ncpa.cpl, right-click your active adapter, choose Properties, and uncheck Internet Protocol Version 6 (TCP/IPv6), then click OK. On a Mac, go to System Settings, then Network, open your connection's details, and set Configure IPv6 to Link-local only. Reload the page and see whether the error is gone.
- Update or reinstall the network adapter driver. A buggy or outdated Wi-Fi driver can drop and reconnect the adapter on its own, which Chrome reports as a network change. On Windows, press Win+X, choose Device Manager, expand Network adapters, right-click your Wi-Fi or Ethernet adapter, and choose Update driver, then Search automatically for drivers. If no update is found, right-click the adapter again, choose Uninstall device, restart the computer, and let Windows reinstall the driver automatically. On a Mac, install any pending macOS updates, since network drivers ship with the system. If the error only happens on one laptop while other devices are fine, a failing adapter is likely, and a USB Wi-Fi adapter is a cheap way to confirm it.
Did this fix it? Quick checklist
- The page loads without ERR_NETWORK_CHANGED
- Other websites load normally on the same network
- The error stays gone after the router restart settles
- The error does not return when the VPN reconnects
If the page loads on your phone's hotspot but not on home Wi-Fi, your router or its link to your ISP is the fault — the restart in step 4 fixes most of these, and a router older than five years is worth replacing. If the error only appears while a VPN is active, the VPN's server switching is the cause: pin it to one stable server or leave it off while browsing. If only one laptop shows the error while other devices are fine, the adapter driver in step 6 is the fix that matters.
Frequently asked questions
What does ERR_NETWORK_CHANGED mean?
It means Chrome started loading a page on one network connection, and before the page finished, the device's connection changed — you switched Wi-Fi networks, a VPN connected or disconnected, the router gave you a new IP address, or the adapter dropped and reconnected. Chrome stops the half-finished load rather than mixing data from two different connections, and shows this error instead.
Why does ERR_NETWORK_CHANGED keep happening when I switch Wi-Fi networks?
Switching networks in the middle of a load is the classic trigger: the page request went out on the old network, and by the time the response comes back, your device is on a new one with a different IP address. Wait until the new network is fully connected, with the Wi-Fi icon settled and no warning triangle, before loading pages, and reload once if a tab was already open during the switch.
Can a VPN cause ERR_NETWORK_CHANGED?
Yes, and it is one of the most common causes. Every time a VPN connects, disconnects, or switches servers, your device's network path changes, and any page loading at that moment fails with this error. The fix is to connect the VPN before you start browsing, keep it on one stable server, and reload any tab that was open during the switch.
How is ERR_NETWORK_CHANGED different from ERR_INTERNET_DISCONNECTED?
ERR_NETWORK_CHANGED means your connection changed in the middle of a load, but a working connection still exists — reload usually fixes it. ERR_INTERNET_DISCONNECTED means there is no internet path at all, so nothing can load until the connection itself is restored. If only one tab fails right after a network or VPN switch, it is the network-changed error; if every site fails, it is the disconnected error.