Suddenly, things aren’t loading properly. For example Heimdall takes forever to load and Navidrome is timing out.
When I do docker-compose pull
It says says
Error response from daemon: Get "https://registry-1.docker.io/v2/" net/http: request cancelled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Anyone know what’s up or how to fix it?
Edit: checking the /etc/resolv.conf
It says
search cable.virginm.net
nameserver 194.168.4.100
nameserver 194.168.8.100
Though neither are opening anything from a browser
Not sure if it’s helpful, but this is what the networking bridge says via Portainer
Network details
Name: bridge
Id: Oc3f5ce6ffc566ee80/1689056f11d491269849967877933858053581742-978
Driver: bridge
Scope: local
Attachable: false
Internal: false
IPV4 Subnet - 172.120.0/16: IPV4 Gateway - 172.17.0.1
IPV4 P Range: PV4 Excluded IPs
Access control
Ownership: public
Network options
com.docker network.bridge default_bridge: true
com.docker.network.bridge.enable.icc: true
com docket.network.bridge.enable_ip.masquerade: true
com docker.network.bridge.host_binding_ipv4: 0.0.0.0
com.docker.network.bridge.name: docker0
com.docker.network.driver.mtu: 1500
I suspect it may be this bug https://github.com/moby/moby/issues/47662
##Resolution Turns out it was just Virgin Media’s router doing shit. A factory reset of the router fixed my issues.
I would try momentarily replacing the defined dns servers with
nameserver 1.1.1.1and see if stuff improves, though the pull error would hint that docker did resolve the name but somehow didn’t get an answer.
Hard to guess what else could be a problem apart from some obvious stuff - check if the internet connection is healthy and stable (ping, watch for spikes in ms or drops, also any outgoing firewall filters?)Just want to say thank you for your kindness!
So it was DNS?
Either DNS or DHCP
Check for PSI stalling in htop (add PSI meters for cpu, ram, and io in the config menu), to rule out your system being overloaded. Check internet connectivity with ping 1.1.1.1, and see why registry is timing out with
curl -v https://registry-1.docker.io/v2/You can also test your dns servers if you think that they are an issue with
dig registry-1.docker.io @1.1.1.1 dig registry-1.docker.io @194.168.4.100If the dig command outputs differ from each other, then it is likely that your ISP’s DNS servers are faulty and you should switch nameservers to 1.1.1.1 and 1.0.0.1 like the other commenter said.
HTOP shows CPU, memory and IO all moderately low.
Ping shows
55 packets transmitted, 49 received, 10.9091% packet loss, time 54221ms rtt min/avg/max/mdev = 50.922/712.756/1784.732/378,340 ms, pipe 2Your internet/wifi seems really overloaded, average ping rtt should be under 100ms, not 712ms. Your wifi signal might be bad, a computer may be downloading/uploading a lot of data, or there is an issue with your internet line.
Double check your wifi signal and computer traffic, maybe try using a direct wired ethernet connection and disconnecting all other computers. Otherwise, contact your ISP with these ping results and speed results from speedtest.net.
Thank you. I ended up calling my ISP and their automation fobbed me off and recommended a factory reset of my router. That actually fixed my issues.
Bruh you’re losing 10% of all packets, and the ones making it through are taking entire seconds? No wonder it’s not working. Check your physical network connections.
I started seeing this too. Interestingly pulling individual images works, it only does this when trying to pull all the images.
That sounds like it could be load issue. That maybe checking your router could fix your issues as it did mine.
