mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-15 21:31:24 -05:00
[GH-ISSUE #2801] Traefik can't connect all of a sudden #13050
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#13050
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @roadkingvrod on GitHub (Apr 7, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2801
Describe the Bug
Running EE. Not sure if it's tied to the upgrade or something got corrupted.
-v02.api.letsencrypt.org/directory providerName=letsencrypt.acme
2026-04-07T03:58:12Z ERR Provider error, retrying in 494.617452ms error="cannot fetch configuration data: do fetch request: Get "http://pangolin:3001/api/v1/traefik-config": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" providerName=http
2026-04-07T03:58:18Z ERR Provider error, retrying in 262.285775ms error="cannot fetch configuration data: do fetch request: Get "http://pangolin:3001/api/v1/traefik-config": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" providerName=http
2026-04-07T03:58:23Z ERR Provider error, retrying in 558.980307ms error="cannot fetch configuration data: do fetch request: Get "http://pangolin:3001/api/v1/traefik-config": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" providerName=http
Environment
To Reproduce
Launch the compose file.
Expected Behavior
Work like it did before.
@LaurenceJJones commented on GitHub (Apr 7, 2026):
Can you check that pangolin the container is running? typically traefik wont start if pangolin is unhealthy.
Or check for any errors within the pangolin container logs.
@roadkingvrod commented on GitHub (Apr 8, 2026):
Thanks for responding. After some digging around, it appears that the logging issue is back. I haven't made any recent changes (still had them at 3 days), but after this current version, everything was very slow. Once I turned off logging again, it sped right up.
Not sure if it was a regression or maybe my disk just can't keep up (it's a home lab)
@m-elsharkawi commented on GitHub (Apr 13, 2026):
I found what was causing a similar issue for me. Docker bridge networking on the host was broken by stale nftables raw PREROUTING rules left behind after the outage and network recreation.
Symptoms were:
In my case,
pangolinandgerbilwere on the same bridge, butnft list rulesetshowed old rules like these still dropping traffic:Those rules were stale and no longer matched the current bridge.
What fixed it:
Identify the stale drop rules for the affected container IPs.
Delete the bad rules by handle:
In my case, removing the stale rules immediately restored container-to-container connectivity and Pangolin started working again.
A Docker restart alone did not remove those stale rules, so checking
nftdirectly was the key.@github-actions[bot] commented on GitHub (Apr 28, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (May 13, 2026):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.