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.

  • sabreW4K3OP
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    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 2
    
    • Justin@lemmy.jlh.name
      link
      fedilink
      English
      arrow-up
      3
      ·
      9 months ago

      Your 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.

      • sabreW4K3OP
        link
        fedilink
        English
        arrow-up
        2
        ·
        9 months ago

        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.

    • catloaf@lemm.ee
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 months ago

      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.