39

When I use Google Chrome (currently 61, but the error exists before), I constantly get ERR_NETWORK_CHANGED. Often, the webpage reloads and works a second later, but often things simply don't work. For example, I'm not able to download files from Google Drive at all, because a XHR call fails with this error (this is an example. The error is not specific to Google Drive). Social logins with Google / Facebook are not possible, because the callback after the login are failing, too. The problem exists in incognito mode, too.

With Firefox, there seem to be no problems.

On Ubuntu 16.04, the problem doesn't exist.

Ethernet controller is a I219-V. Not able to try other machines.

While writing this, I found out that disabling the IPv6 privacy extensions with 

sudo sysctl -w net.ipv6.conf.enp0s31f6.use_tempaddr=0

and restarting the interface seem to be a workaround solve the problem, but obviously it's bad to use workarounds instead of solving the root problem.

  1. Whats going on here? Why does this affect Chrome and not Firefox? What is the difference?
  2. Whats the difference between Ubuntu 17.04 and 16.04 regarding this problem?
  3. How can I get more information about the problem?
  4. Is this a known problem with Ubuntu 17.04?
Eliah Kagan
  • 117,780
Krangerich
  • 730

4 Answers4

75

For anyone else that probably didn't think of it like me - this was being caused by a docker container I had running on the machine.

Dale King
  • 879
  • 5
    What did the docker container do? Just run? – phihag Nov 13 '19 at 12:18
  • 5
    This worked for me. The container in question may have been failing and restarting endlessly since boot but was otherwise unremarkable. docker ps; docker update <container_id> --restart=no; – bbeecher May 04 '20 at 23:02
  • 2
    yes, in my case i forgot a couple of containers failing and rebooting with "pip install -r requirements/local.txt" as command, this screw up my internet connection. – Diego Puente Oct 06 '20 at 14:18
  • 2
    In my case, several containers periodically failed. This disrupted the Internet connection. – IStranger Aug 02 '21 at 21:05
  • 1
    I didn't believe this before, but indeed I saw that one docker container in my computer keeps restarting. Once I stop it the error is gone. I will really appreciate if somebody can give an explanation on how docker restart can disrupt the internet connection. – Jon Kartago Lamida Mar 07 '22 at 06:29
  • oh I don't run any container but my chrome still have same issue. I tried to install Brave browser but still same. Only Firefox is working normally – huykon225 Apr 21 '23 at 09:57
4

Making a js request while starting a docker container seems to trigger this kind of error. Somehow connected with the docker network, when containers are dynamically added/removed. Chromium only, not seen on Firefox.

Кристиян Кацаров
  • 343
4

This still happens in Ubuntu 18.04 and Google Chrome Stable (80.0.3987.106 now).

Disabling Docker reduces (not eliminate) this issue, and using sysctl to disable use_tempaddr also reduces too (still didn't eliminate).

I need to totally disable IPv6 to avoid this issue, by changing /etc/default/grub from:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

To:

GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet splash"

Then running Docker would be fine.

Gea-Suan Lin
  • 406
  • 4
  • 7
2

Alternately, the following lines can be added to /etc/sysctl.conf to disable IPv6 permanently.

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
sudar
  • 47