When the whole stack starts up again, sometime traefik will be unable to reach pangolin.
This will continue until traefik is restarted and has become a big annoyance.
Pangolin was installed using the installer script.
traefik | 2026-01-22T06:46:17Z ERR Provider error, retrying in 5.462830427s 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:36143->127.0.0.11:53: read: connection refused" providerName=http
There was a previous issue about this, but was closed due to inactivity: #438
Environment
OS Type & Version: Ubuntu 24.04.3 LTS
Pangolin Version: 1.14.1
Gerbil Version: 1.3.0
Traefik Version: v.3.6.7
Newt Version: v.1.8.1
Olm Version: Not using
To Reproduce
Usually happens after a reboot of the system when every docker container is starting up.
Expected Behavior
I expect traefik to be able to host other sites than only the pangolin dashbaord, but I also want traefik to atleast resolve it self after awhile.
Originally created by @SteelyxYT on GitHub (Jan 27, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2346
### Describe the Bug
When the whole stack starts up again, sometime traefik will be unable to reach pangolin.
This will continue until traefik is restarted and has become a big annoyance.
Pangolin was installed using the installer script.
`traefik | 2026-01-22T06:46:17Z ERR Provider error, retrying in 5.462830427s 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:36143->127.0.0.11:53: read: connection refused" providerName=http`
There was a previous issue about this, but was closed due to inactivity: #438
### Environment
- OS Type & Version: Ubuntu 24.04.3 LTS
- Pangolin Version: 1.14.1
- Gerbil Version: 1.3.0
- Traefik Version: v.3.6.7
- Newt Version: v.1.8.1
- Olm Version: Not using
### To Reproduce
Usually happens after a reboot of the system when every docker container is starting up.
### Expected Behavior
I expect traefik to be able to host other sites than only the pangolin dashbaord, but I also want traefik to atleast resolve it self after awhile.
My current janky fix was just making a script to kill traefik when specific endpoints not reached and set it as entrypoint and having docker restart the container. Could have used another service to monitor health and restart it, but I wanted to limit the amount of services I created.
<!-- gh-comment-id:3805613033 -->
@SteelyxYT commented on GitHub (Jan 27, 2026):
My current janky fix was just making a script to kill traefik when specific endpoints not reached and set it as entrypoint and having docker restart the container. Could have used another service to monitor health and restart it, but I wanted to limit the amount of services I created.
@oschwartz10612 commented on GitHub (Jan 27, 2026):
This is because of the service:gerbil in the network config of the
traefik container. If the gerbil container restarts and the traefik
container does not then its network stack is orphaned and cant access
pangolin.
I have observed this issue myself. Best practice for restarting the
stack can sometimes be just doing a full docker compose down then up. If
anyone wants to chime in with a fix for this them let me know.
<!-- gh-comment-id:3807751983 -->
@oschwartz10612 commented on GitHub (Jan 27, 2026):
This is because of the service:gerbil in the network config of the
traefik container. If the gerbil container restarts and the traefik
container does not then its network stack is orphaned and cant access
pangolin.
I have observed this issue myself. Best practice for restarting the
stack can sometimes be just doing a full docker compose down then up. If
anyone wants to chime in with a fix for this them let me know.
I have also noticed that if the badger plugin takes too long to fetch it will completly disable it and making all endpoints that rely on the plugin to fail:
2026-01-27T21:43:42Z INF Loading plugins... plugins=["badger"]
2026-01-27T21:43:54Z ERR Plugins are disabled because an error has occurred. error="unable to set up plugins environment: unable to install plugin badger: unable to download plugin github.com/fosrl/badger: failed to call service: Get \"https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.3.1\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" plugins=["badger"]
2026-01-27T21:55:37Z ERR error="invalid middleware \"badger@http\" configuration: invalid middleware type or middleware does not exist" entryPointName=websecure routerName=2-REDACTED-router@http
2026-01-27T21:55:37Z ERR error="invalid middleware \"badger@http\" configuration: invalid middleware type or middleware does not exist" entryPointName=websecure routerName=10-REDACTED-router@http
2026-01-27T21:55:37Z ERR error="invalid middleware \"badger@http\" configuration: invalid middleware type or middleware does not exist" entryPointName=websecure routerName=13-REDACTED-router@http
<!-- gh-comment-id:3807800317 -->
@SteelyxYT commented on GitHub (Jan 27, 2026):
I have also noticed that if the badger plugin takes too long to fetch it will completly disable it and making all endpoints that rely on the plugin to fail:
```
2026-01-27T21:43:42Z INF Loading plugins... plugins=["badger"]
2026-01-27T21:43:54Z ERR Plugins are disabled because an error has occurred. error="unable to set up plugins environment: unable to install plugin badger: unable to download plugin github.com/fosrl/badger: failed to call service: Get \"https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.3.1\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" plugins=["badger"]
```
```
2026-01-27T21:55:37Z ERR error="invalid middleware \"badger@http\" configuration: invalid middleware type or middleware does not exist" entryPointName=websecure routerName=2-REDACTED-router@http
2026-01-27T21:55:37Z ERR error="invalid middleware \"badger@http\" configuration: invalid middleware type or middleware does not exist" entryPointName=websecure routerName=10-REDACTED-router@http
2026-01-27T21:55:37Z ERR error="invalid middleware \"badger@http\" configuration: invalid middleware type or middleware does not exist" entryPointName=websecure routerName=13-REDACTED-router@http
```
This is because of the service:gerbil in the network config of the
traefik container. If the gerbil container restarts and the traefik
container does not then its network stack is orphaned and cant access
pangolin.
I have observed this issue myself. Best practice for restarting the
stack can sometimes be just doing a full docker compose down then up. If
anyone wants to chime in with a fix for this them let me know.
I think there is not really a fix, because that is how docker works.
You have to restart the full Stack and not only gerbil.
<!-- gh-comment-id:3818263782 -->
@Blacks-Army commented on GitHub (Jan 29, 2026):
> This is because of the service:gerbil in the network config of the
> traefik container. If the gerbil container restarts and the traefik
> container does not then its network stack is orphaned and cant access
> pangolin.
>
> I have observed this issue myself. Best practice for restarting the
> stack can sometimes be just doing a full docker compose down then up. If
> anyone wants to chime in with a fix for this them let me know.
>
I think there is not really a fix, because that is how docker works.
You have to restart the full Stack and not only gerbil.
I have also noticed that if the badger plugin takes too long to fetch it will completly disable it and making all endpoints that rely on the plugin to fail:
2026-01-27T21:43:42Z INF Loading plugins... plugins=["badger"]
2026-01-27T21:43:54Z ERR Plugins are disabled because an error has occurred. error="unable to set up plugins environment: unable to install plugin badger: unable to download plugin github.com/fosrl/badger: failed to call service: Get \"https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.3.1\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" plugins=["badger"]
2026-01-27T21:55:37Z ERR error="invalid middleware \"badger@http\" configuration: invalid middleware type or middleware does not exist" entryPointName=websecure routerName=2-REDACTED-router@http
2026-01-27T21:55:37Z ERR error="invalid middleware \"badger@http\" configuration: invalid middleware type or middleware does not exist" entryPointName=websecure routerName=10-REDACTED-router@http
2026-01-27T21:55:37Z ERR error="invalid middleware \"badger@http\" configuration: invalid middleware type or middleware does not exist" entryPointName=websecure routerName=13-REDACTED-router@http
This happens because traefik first reads the static and dynamic file config before pulling the config from pangolin.
A fix would be to just 'touch' a file in the dynamic config of traefik by adding and deleting a file, so it rereads the config.
<!-- gh-comment-id:3818279020 -->
@Blacks-Army commented on GitHub (Jan 29, 2026):
> I have also noticed that if the badger plugin takes too long to fetch it will completly disable it and making all endpoints that rely on the plugin to fail:
> ```
> 2026-01-27T21:43:42Z INF Loading plugins... plugins=["badger"]
> 2026-01-27T21:43:54Z ERR Plugins are disabled because an error has occurred. error="unable to set up plugins environment: unable to install plugin badger: unable to download plugin github.com/fosrl/badger: failed to call service: Get \"https://plugins.traefik.io/public/download/github.com/fosrl/badger/v1.3.1\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" plugins=["badger"]
> ```
> ```
> 2026-01-27T21:55:37Z ERR error="invalid middleware \"badger@http\" configuration: invalid middleware type or middleware does not exist" entryPointName=websecure routerName=2-REDACTED-router@http
> 2026-01-27T21:55:37Z ERR error="invalid middleware \"badger@http\" configuration: invalid middleware type or middleware does not exist" entryPointName=websecure routerName=10-REDACTED-router@http
> 2026-01-27T21:55:37Z ERR error="invalid middleware \"badger@http\" configuration: invalid middleware type or middleware does not exist" entryPointName=websecure routerName=13-REDACTED-router@http
> ```
This happens because traefik first reads the static and dynamic file config before pulling the config from pangolin.
A fix would be to just 'touch' a file in the dynamic config of traefik by adding and deleting a file, so it rereads the config.
@github-actions[bot] commented on GitHub (Feb 13, 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.
<!-- gh-comment-id:3894167982 -->
@github-actions[bot] commented on GitHub (Feb 13, 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 (Feb 28, 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.
<!-- gh-comment-id:3975861541 -->
@github-actions[bot] commented on GitHub (Feb 28, 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.
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 @SteelyxYT on GitHub (Jan 27, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2346
Describe the Bug
When the whole stack starts up again, sometime traefik will be unable to reach pangolin.
This will continue until traefik is restarted and has become a big annoyance.
Pangolin was installed using the installer script.
traefik | 2026-01-22T06:46:17Z ERR Provider error, retrying in 5.462830427s 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:36143->127.0.0.11:53: read: connection refused" providerName=httpThere was a previous issue about this, but was closed due to inactivity: #438
Environment
To Reproduce
Usually happens after a reboot of the system when every docker container is starting up.
Expected Behavior
I expect traefik to be able to host other sites than only the pangolin dashbaord, but I also want traefik to atleast resolve it self after awhile.
@SteelyxYT commented on GitHub (Jan 27, 2026):
My current janky fix was just making a script to kill traefik when specific endpoints not reached and set it as entrypoint and having docker restart the container. Could have used another service to monitor health and restart it, but I wanted to limit the amount of services I created.
@oschwartz10612 commented on GitHub (Jan 27, 2026):
This is because of the service:gerbil in the network config of the
traefik container. If the gerbil container restarts and the traefik
container does not then its network stack is orphaned and cant access
pangolin.
I have observed this issue myself. Best practice for restarting the
stack can sometimes be just doing a full docker compose down then up. If
anyone wants to chime in with a fix for this them let me know.
@SteelyxYT commented on GitHub (Jan 27, 2026):
I have also noticed that if the badger plugin takes too long to fetch it will completly disable it and making all endpoints that rely on the plugin to fail:
@Blacks-Army commented on GitHub (Jan 29, 2026):
I think there is not really a fix, because that is how docker works.
You have to restart the full Stack and not only gerbil.
@Blacks-Army commented on GitHub (Jan 29, 2026):
This happens because traefik first reads the static and dynamic file config before pulling the config from pangolin.
A fix would be to just 'touch' a file in the dynamic config of traefik by adding and deleting a file, so it rereads the config.
@github-actions[bot] commented on GitHub (Feb 13, 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 (Feb 28, 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.