Discussion
Loading...
@rolle this was also a very widespread problem with Chrome on macOS. Chrome did solve it finally, but I don’t think there was a single cause for “network changing”. Chrome just cared for changes that didn’t really affect its networking
@oivaeskola I think mine was a unique corner case: https://mementomori.social/@rolle/114958673827201870
@rolle yeah, just meant that it’s a common problem for whatever reasons. Also this was the next toot on my timeline: https://rosafamily.social/@arthur/114957136910282078
I have narrowed this issue down to Vivaldi. Does not happen with ungoogled-chromium. I'm going to switch back to it, too frustrating to deal with this.
EDIT... I take that back, it's still everywhere.
I just ran
sudo dhclient -r
sudo dhclient
sudo systemctl restart NetworkManager
nmcli networking off
nmcli networking on
sudo nextdns upgrade
sudo nextdns restart
Monitoring:
sudo journalctl -xeu NetworkManager -f
sudo journalctl -u nextdns.service -f
This is revealing...
elo 02 13:13:18 infinity nextdns[114716]: Network change detected: docker0 flag up|broadcast|multicast -> up|broadcast|multicast|running
elo 02 13:13:28 infinity nextdns[114716]: Network change detected: docker0 flag up|broadcast|multicast|running -> up|broadcast|multicast
elo 02 13:13:38 infinity nextdns[114716]: Network change detected: docker0 flag up|broadcast|multicast -> up|broadcast|multicast|running
elo 02 13:13:58 infinity nextdns[114716]: Network change detected: docker0 flag up|broadcast|multicast|running -> up|broadcast|multicast
elo 02 13:14:08 infinity nextdns[114716]: Network change detected: docker0 flag up|broadcast|multicast -> up|broadcast|multicast|running
It was looping docker after all! Wtf.
Solution:
ip addr show | grep 'inet ' | awk '{print $2}' | cut -d/ -f1
sudo nextdns install -listen :53
sudo systemctl restart nextdns
sudo systemctl restart docker.socket
sudo systemctl restart docker.service
Custom DNS is now binded to main network ignoring docker. I may have tried some docker containers a couple of days ago and somehow the network got stuck. Very weird indeed.
This solves all my Mastodon issues as well that were caused by ERR_NETWORK_CHANGED breaking all the APIs and scripts it uses. Instead of looking at my Console I thought it was a bug in Mastodon nightly... 
Sometimes I hate networking.
Glad I slept a little.
@rolle Oof. And rolling custom means you know that will likely cause other issues… eventually - probably just far enough in the future for you to have forgotten about this fix. 🤔🤣
@rolle could it be your isp
@lndn I doubt it. The have not reported issues.
@rolle oh ok
@rolle @lndn I dunno, my experience is that they're not always aware or even able to fix their stuff. For years I had an issue with modem sometimes forcefully being unable to reconnect, and had to manually go run "fix issue" self service using other connection. That fixed it, but their automated message claimed the problem would be on my side. Resetting hardware etc. never fixed anything for me.
Of course totally different case except for the point of ISP knowing about their issues.
@Merri
True, but it was not ISP this time.
Solved it on my own: https://mementomori.social/@rolle/114958673827201870
@rolle @Vivaldi
This forum post might be helpful.
I hope for resolution. 
Continuous error ERR_NETWORK_CHANGED | Vivaldi Forum
https://forum.vivaldi.net/topic/84874/continuous-error-err_network_changed
@nibushibu@social.vivaldi.net @rolle@mementomori.social @Vivaldi@social.vivaldi.net If one is randomizing their Wifi MAC address frequently and getting a new IP address from their WLAN router then according to that forum post that would cause it because new MAC + DHCP = new ip address
@rolle@mementomori.social @Vivaldi@social.vivaldi.net
Doesn't Vivaldi include a VPN? Perhaps it's related to that?
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled