Describe the Bug
This has been a great piece of software for several months! Loved it thoroughly with minimal issues.
Woke up this morning and it is locked up, unable to get logged into the pangolin dashboard, and it is not passing traffic. the logs show up with.
gerbil | INFO: 2025/12/12 16:49:07 Failed to report peer bandwidth: API returned non-OK status: 403 Forbidden
I can restart the compose stack and it will work for a small amount of time before those error messages start popping up, and it stops the traffic again. If i am logged into the dashboard, i cannot make any changes, or even log out. If i am not logged in, i cannot log in.
i started working my way through updates but it didn't seem to make any difference, so I paused on that before coming across breaking changes?
I changed the gerbil port per one of the pull requests.
Environment
- OS Type & Version: Debian 6.1.158-1 (2025-11-09) x86_64
- Pangolin Version: started on 1.8.0 and has persisted through all updates to 1.9.4
- Gerbil Version: started on version 1.1.0 and persisted through 1.3.0
- Traefik Version: started on the original version (not sure) but persisted through 3.6.4
- Newt Version:started on 1.6.0 and is still there on 1.7.0
- Olm Version: (if applicable) n/a
To Reproduce
restart the docker compose stack and wait a few minutes. If I get impatient, i can walk to the other side of the house, and sure enough when i come back, the gerbil error about peer bandwidth returns.
I have two WAPs in my house, and i do roam back and forth, is that relevant?
Expected Behavior
The normal pangolin thang
Describe the Bug
This has been a great piece of software for several months! Loved it thoroughly with minimal issues.
Woke up this morning and it is locked up, unable to get logged into the pangolin dashboard, and it is not passing traffic. the logs show up with.
gerbil | INFO: 2025/12/12 16:49:07 Failed to report peer bandwidth: API returned non-OK status: 403 Forbidden
I can restart the compose stack and it will work for a small amount of time before those error messages start popping up, and it stops the traffic again. If i am logged into the dashboard, i cannot make any changes, or even log out. If i am not logged in, i cannot log in.
i started working my way through updates but it didn't seem to make any difference, so I paused on that before coming across breaking changes?
I changed the gerbil port per one of the pull requests.
Environment
To Reproduce
restart the docker compose stack and wait a few minutes. If I get impatient, i can walk to the other side of the house, and sure enough when i come back, the gerbil error about peer bandwidth returns.
I have two WAPs in my house, and i do roam back and forth, is that relevant?
Expected Behavior
The normal pangolin thang