github-starred/gerbil
2
0
Fork 0
mirror of https://github.com/fosrl/gerbil.git synced 2026-05-09 12:27:44 -05:00
Code Issues 43 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #47] Gerbil Failed to report peer bandwidth: API returned non-OK status: 403 Forbidden #293

New Issue
Closed
opened 2026-05-08 12:07:11 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-08 12:07:11 -05:00
Owner
Copy Link

Originally created by @nckwdfrm on GitHub (Dec 12, 2025).
Original GitHub issue: https://github.com/fosrl/gerbil/issues/47

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

Originally created by @nckwdfrm on GitHub (Dec 12, 2025). Original GitHub issue: https://github.com/fosrl/gerbil/issues/47 ### 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
GiteaMirror commented 2026-05-08 12:07:12 -05:00
Author
Owner
Copy Link

@nckwdfrm commented on GitHub (Dec 12, 2025):

This error returns even with no newt client connected since the stack had been restarted,

<!-- gh-comment-id:3647748324 --> @nckwdfrm commented on GitHub (Dec 12, 2025): This error returns even with no newt client connected since the stack had been restarted,
GiteaMirror commented 2026-05-08 12:07:12 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Dec 12, 2025):

I think this gerbil log message is probably not the cause but a symptom
of pangolin crashing. Could you share the pangolin logs when this crash
occurs? It would also be good to put it into debug mode for this in
config.yml.

Do you have any server symptoms like a full disk or anything like that?

<!-- gh-comment-id:3647885171 --> @oschwartz10612 commented on GitHub (Dec 12, 2025): I think this gerbil log message is probably not the cause but a symptom of pangolin crashing. Could you share the pangolin logs when this crash occurs? It would also be good to put it into debug mode for this in config.yml. Do you have any server symptoms like a full disk or anything like that?
GiteaMirror commented 2026-05-08 12:07:13 -05:00
Author
Owner
Copy Link

@nckwdfrm commented on GitHub (Dec 18, 2025):

Well, after another update or two, it appears to be doing well. Closing!

<!-- gh-comment-id:3670761540 --> @nckwdfrm commented on GitHub (Dec 18, 2025): Well, after another update or two, it appears to be doing well. Closing!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gerbil#293
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?