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.

you are viewing a single comment's thread
view the rest of the comments
[–] 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!