LightAtom

ERR_NETWORK_CHANGED: Why It Happens and How to Stop It

Chrome saw your network connection change while loading the page, for example a Wi-Fi switch, a VPN reconnecting or a virtual network adapter appearing.

ERR_NETWORK_CHANGED

Your network changed in the middle of loading: an address, interface or route changed, so Chrome dropped the connection to avoid sending data over the wrong path.

Quick checks

  • Reload: one-off cases happen when you switch networks.
  • Note whether it happens when a VPN connects or Wi-Fi roams.
  • Check whether Ethernet and Wi-Fi are both connected and fighting.

Fixes on Mac

  1. Stop Wi-Fi from hopping

    1. System Settings › Wi-Fi › Advanced: remove old networks and turn off Auto-Join for weak ones nearby.

  2. Set the service order

    1. System Settings › Network › ⋯ › Set Service Order: put your main connection first.
    2. Turn off services you don't use (Thunderbolt Bridge, old VPNs).

  3. Check VPNs and virtual adapters

    1. VPNs that reconnect, Docker, virtual machines and network extensions add and remove interfaces.
    2. Run ifconfig -l and look for interfaces that appear and disappear.

Fixes on Windows

  1. Disable unused adapters

    1. Control Panel › Network Connections: disable virtual adapters you don't need.
    2. Run ipconfig /release, ipconfig /renew, netsh winsock reset.

Other devices

  1. Router

    1. If IPv6 addresses change constantly, update the router firmware.

Still not working?

Frequent network changes on a stable network point to a flaky Wi-Fi link (signal drops), a router renewing leases too often, or software adding interfaces. Watch it live: LightAtom shows connections dropping, and log stream --predicate 'subsystem == "com.apple.network"' in Terminal shows network events.

See what’s happening

LightAtom's connections view shows connections being dropped and re-created when your network changes.

Frequently asked questions

What does ERR_NETWORK_CHANGED mean?

Chrome detected a change in your network (a new IP, interface or route) while loading, and stopped the request. Reloading after the change usually works.

Why does ERR_NETWORK_CHANGED keep happening?

Something keeps changing the network: Wi-Fi roaming between access points, a VPN reconnecting, Docker or VM adapters, or both Ethernet and Wi-Fi switching priority.

Can IPv6 cause ERR_NETWORK_CHANGED?

Yes. Routers that keep changing IPv6 prefixes or addresses trigger it. Updating the router or disabling IPv6 on the router can help.

Related errors and tools

Related

LightAtom team

The people who build LightAtom, a network monitor for macOS.