Traefik logs: Unable to fetch config data for pangolin api #198

Closed
opened 2025-11-13 11:52:44 -06:00 by GiteaMirror · 7 comments
Owner

Originally created by @notc137 on GitHub (Mar 31, 2025).

Just installed pangolin today and have run into this issue twice sadly. First time it occured I was working on setting up geoip blocking plugin in traefik, after rebooting the docker stack, I had gotten the following error

{"level":"error","providerName":"http","error":"cannot fetch configuration data: do fetch request: Get \"http://pangolin:3001/api/v1/traefik-config\": dial tcp: lookup pangolin on 127.0.0.11:53: read udp 127.0.0.1:40988->127.0.0.11:53: read: connection refused","time":"2025-03-31T02:18:12Z","message":"Provider error, retrying in 6.533049333s"}

Reverted all my changes and still was unable to recover from this error. Chalked it up to I messed something up but since it was pretty much brand new instance I just rebuilt from scratch.

Second time this same error has occurred was just now. Got alerted one of my sites went down, went to investigate and could not reach the site. Looking through logs everything was fine, was able to get the pangolin admin page. After some digging, crowdsec seemed to have banned my public IP for whatever reason (still getting around to fully mess with and configure it). I whitelisted my IP in crowdsec and rebooted my entire docker stack and now I am getting hte same exact error in traefik.

I checked all the logs in crowdsec and pangolin and everything is up and running as expected. Its just traefik.

Update:

when I run the following:
docker compose down && docker system prune -af && docker compose up -d

everything starts to work again with no issues.

I noticed another part of the log file had an issue earlier up that only occurs on reboot. It is the following
{"level":"error","error":{"Op":"Get","URL":"[https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0","Err":%7B%7D%7D,"method":"GET","url":"https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0","time":"2025-03-30T11:53:41Z","message":"Request](https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0%22,%22Err%22:%7B%7D%7D,%22method%22:%22GET%22,%22url%22:%22https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0%22,%22time%22:%222025-03-30T11:53:41Z%22,%22message%22:%22Request) failed"} traefik | {"level":"error","plugins":["badger","crowdsec"],"error":"unable to set up plugins environment: unable to download plugin github.com/fosrl/badger: failed to call service: Get "https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0/": GET https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0 giving up after 4 attempt(s): Get "https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)","time":"2025-03-30T11:53:41Z","message":"Plugins are disabled because an error hasoccurred."}`

Originally created by @notc137 on GitHub (Mar 31, 2025). Just installed pangolin today and have run into this issue twice sadly. First time it occured I was working on setting up geoip blocking plugin in traefik, after rebooting the docker stack, I had gotten the following error `{"level":"error","providerName":"http","error":"cannot fetch configuration data: do fetch request: Get \"http://pangolin:3001/api/v1/traefik-config\": dial tcp: lookup pangolin on 127.0.0.11:53: read udp 127.0.0.1:40988->127.0.0.11:53: read: connection refused","time":"2025-03-31T02:18:12Z","message":"Provider error, retrying in 6.533049333s"}` Reverted all my changes and still was unable to recover from this error. Chalked it up to I messed something up but since it was pretty much brand new instance I just rebuilt from scratch. Second time this same error has occurred was just now. Got alerted one of my sites went down, went to investigate and could not reach the site. Looking through logs everything was fine, was able to get the pangolin admin page. After some digging, crowdsec seemed to have banned my public IP for whatever reason (still getting around to fully mess with and configure it). I whitelisted my IP in crowdsec and rebooted my entire docker stack and now I am getting hte same exact error in traefik. I checked all the logs in crowdsec and pangolin and everything is up and running as expected. Its just traefik. Update: when I run the following: `docker compose down && docker system prune -af && docker compose up -d` everything starts to work again with no issues. I noticed another part of the log file had an issue earlier up that only occurs on reboot. It is the following `{"level":"error","error":{"Op":"Get","URL":"[https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0","Err":%7B%7D%7D,"method":"GET","url":"https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0","time":"2025-03-30T11:53:41Z","message":"Request](https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0%22,%22Err%22:%7B%7D%7D,%22method%22:%22GET%22,%22url%22:%22https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0%22,%22time%22:%222025-03-30T11:53:41Z%22,%22message%22:%22Request) failed"} traefik | {"level":"error","plugins":["badger","crowdsec"],"error":"unable to set up plugins environment: unable to download plugin github.com/fosrl/badger: failed to call service: Get "https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0/": GET https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0 giving up after 4 attempt(s): Get "https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.0.0/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)","time":"2025-03-30T11:53:41Z","message":"Plugins are disabled because an error has`occurred."}`
GiteaMirror added the stale label 2025-11-13 11:52:44 -06:00
Author
Owner

@miloschwartz commented on GitHub (Mar 31, 2025):

The first cannot fetch configuration data sometimes shows when the stack starts up when the API is not yet fully available. I wouldn't worry about it unless it shows up consistently, like every 5 seconds, and/or it's interrupting functionality.

The second unable to download plugin error, we've seen recently, but I am not yet sure what the cause could be. What OS are you on? Do you happen to be on Debian 12? We're trying to investigate this one, although it could be out of our control with Traefik.

@miloschwartz commented on GitHub (Mar 31, 2025): The first `cannot fetch configuration data` sometimes shows when the stack starts up when the API is not yet fully available. I wouldn't worry about it unless it shows up consistently, like every 5 seconds, and/or it's interrupting functionality. The second `unable to download plugin` error, we've seen recently, but I am not yet sure what the cause could be. What OS are you on? Do you happen to be on Debian 12? We're trying to investigate this one, although it could be out of our control with Traefik.
Author
Owner

@notc137 commented on GitHub (Apr 1, 2025):

I am running Ubuntu 24.04 currently.

cannot fetch configuration data This error lasts the entire time, I let it run for about an hour and still produced that log.

@notc137 commented on GitHub (Apr 1, 2025): I am running Ubuntu 24.04 currently. `cannot fetch configuration data` This error lasts the entire time, I let it run for about an hour and still produced that log.
Author
Owner

@miloschwartz commented on GitHub (Apr 2, 2025):

The Traefik container gets it's config served via an http provider. Pangolin is that provider and serves it over the internal API (default port 3001). Traefik needs to be able to address Pangolin by that address you see in the error. I'd check your set up to make sure that this is possible so that the http requests don't fail every 5 seconds.

@miloschwartz commented on GitHub (Apr 2, 2025): The Traefik container gets it's config served via an http provider. Pangolin is that provider and serves it over the internal API (default port 3001). Traefik needs to be able to address Pangolin by that address you see in the error. I'd check your set up to make sure that this is possible so that the http requests don't fail every 5 seconds.
Author
Owner

@github-actions[bot] commented on GitHub (Apr 16, 2025):

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 (Apr 16, 2025): 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.
Author
Owner

@github-actions[bot] commented on GitHub (Apr 30, 2025):

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.

@github-actions[bot] commented on GitHub (Apr 30, 2025): 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.
Author
Owner

@Exitium-DEV commented on GitHub (Oct 21, 2025):

The Traefik container gets it's config served via an http provider. Pangolin is that provider and serves it over the internal API (default port 3001). Traefik needs to be able to address Pangolin by that address you see in the error. I'd check your set up to make sure that this is possible so that the http requests don't fail every 5 seconds.

having this issue with a fresh install on 24.04 ARM - started happening after changing from CE to EE
Happy to provide any information to help. Zero of my tunnels work as a result.

@Exitium-DEV commented on GitHub (Oct 21, 2025): > The Traefik container gets it's config served via an http provider. Pangolin is that provider and serves it over the internal API (default port 3001). Traefik needs to be able to address Pangolin by that address you see in the error. I'd check your set up to make sure that this is possible so that the http requests don't fail every 5 seconds. having this issue with a fresh install on 24.04 ARM - started happening after changing from CE to EE Happy to provide any information to help. Zero of my tunnels work as a result.
Author
Owner

@Exitium-DEV commented on GitHub (Oct 21, 2025):

@miloschwartz

@Exitium-DEV commented on GitHub (Oct 21, 2025): @miloschwartz
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#198