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.

  • @[email protected]English
    4•9 months ago

    I would try momentarily replacing the defined dns servers with nameserver 1.1.1.1 and 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?)