this post was submitted on 03 Apr 2024
13 points (93.3% liked)

Selfhosted

40183 readers
1084 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
13
[Solved] Sudden Issues (lazysoci.al)
submitted 7 months ago* (last edited 7 months ago) by sabreW4K3@lazysoci.al to c/selfhosted@lemmy.world
12 comments fedilink hide all child comments
 

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.

top 12 comments
sorted by: hot top controversial new old
[–] taaz@biglemmowski.win 4 points 7 months ago* (last edited 7 months ago) (1 children)

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?)

[–] sabreW4K3@lazysoci.al 3 points 7 months ago (1 children)

Just want to say thank you for your kindness!

[–] sznowicki@lemmy.world 2 points 7 months ago (2 children)

So it was DNS?

[–] sabreW4K3@lazysoci.al 2 points 7 months ago

Either DNS or DHCP

[–] jlh@lemmy.jlh.name 3 points 7 months ago (1 children)

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

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

[–] sabreW4K3@lazysoci.al 1 points 7 months ago (2 children)

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
[–] jlh@lemmy.jlh.name 3 points 7 months ago (1 children)

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.

[–] sabreW4K3@lazysoci.al 2 points 7 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 1 points 7 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.

[–] bjornsno@lemm.ee 1 points 7 months ago (1 children)

I started seeing this too. Interestingly pulling individual images works, it only does this when trying to pull all the images.

[–] sabreW4K3@lazysoci.al 1 points 7 months ago

That sounds like it could be load issue. That maybe checking your router could fix your issues as it did mine.