@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.
<!-- gh-comment-id:4198564003 -->
@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.
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)
<!-- gh-comment-id:4203127425 -->
@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)
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:
host -> container worked
container name resolution worked
but container -> container traffic on the same Docker bridge timed out
In my case, pangolin and gerbil were on the same bridge, but nft list ruleset showed old rules like these still dropping traffic:
ip daddr 172.18.0.2 iifname !="docker_gwbridge" drop
ip daddr 172.18.0.3 iifname !="docker_gwbridge" drop
Those rules were stale and no longer matched the current bridge.
What fixed it:
Inspect the nftables raw rules:
sudo nft -a list chain ip raw PREROUTING
Identify the stale drop rules for the affected container IPs.
Delete the bad rules by handle:
sudo nft delete rule ip raw PREROUTING handle <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 nft directly was the key.
<!-- gh-comment-id:4238557700 -->
@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:
* host -> container worked
* container name resolution worked
* but container -> container traffic on the same Docker bridge timed out
In my case, `pangolin` and `gerbil` were on the same bridge, but `nft list ruleset` showed old rules like these still dropping traffic:
```bash
ip daddr 172.18.0.2 iifname != "docker_gwbridge" drop
ip daddr 172.18.0.3 iifname != "docker_gwbridge" drop
```
Those rules were stale and no longer matched the current bridge.
What fixed it:
1. Inspect the nftables raw rules:
```bash
sudo nft -a list chain ip raw PREROUTING
```
2. Identify the stale drop rules for the affected container IPs.
3. Delete the bad rules by handle:
```bash
sudo nft delete rule ip raw PREROUTING handle <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 `nft` directly was the key.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.