github-starred/gerbil
2
0
Fork 0
mirror of https://github.com/fosrl/gerbil.git synced 2026-07-11 09:23:47 -05:00
Code Issues 149 Packages Projects Releases 13 Wiki Activity

[GH-ISSUE #82] Failed to report peer bandwidth: API returned non-OK status: 400 Bad Request #511

New Issue
Open
opened 2026-05-28 23:04:41 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-28 23:04:41 -05:00
Owner
Copy Link

Originally created by @zer0ish on GitHub (May 13, 2026).
Original GitHub issue: https://github.com/fosrl/gerbil/issues/82

Describe the Bug

After updating my Pangolin stack I also updated Gerbil from 1.3 to latest/1.4 and my logs started showing this every 10 seconds. Not sure what is causing this.
Failed to report peer bandwidth: API returned non-OK status: 400 Bad Request

Environment

  • OS Type & Version: Unraid 7.3.0 (Docker compose is used via the GetArcane container).
  • Pangolin Version: 1.18.4
  • Gerbil Version: 1.4 (latest tag)
  • Traefik Version: 3.6
  • Newt Version: Don't have a specific container for Newt. Not using in my case/setup.
  • Olm Version: N/A

To Reproduce

Do incremental updates to pangolin from 1.16 to latest.
Then do updated for Gerbil from 1.3 to latest.

All I did was do updates.
Pangolin is still working but this message won't stop.

Expected Behavior

Not spamming logs every 10 seconds with the message:
Failed to report peer bandwidth: API returned non-OK status: 400 Bad Request

Originally created by @zer0ish on GitHub (May 13, 2026). Original GitHub issue: https://github.com/fosrl/gerbil/issues/82 ### Describe the Bug After updating my Pangolin stack I also updated Gerbil from 1.3 to latest/1.4 and my logs started showing this every 10 seconds. Not sure what is causing this. `Failed to report peer bandwidth: API returned non-OK status: 400 Bad Request` ### Environment - OS Type & Version: Unraid 7.3.0 (Docker compose is used via the GetArcane container). - Pangolin Version: 1.18.4 - Gerbil Version: 1.4 (latest tag) - Traefik Version: 3.6 - Newt Version: Don't have a specific container for Newt. Not using in my case/setup. - Olm Version: N/A ### To Reproduce Do incremental updates to pangolin from 1.16 to latest. Then do updated for Gerbil from 1.3 to latest. All I did was do updates. Pangolin is still working but this message won't stop. ### Expected Behavior Not spamming logs every 10 seconds with the message: `Failed to report peer bandwidth: API returned non-OK status: 400 Bad Request`
GiteaMirror commented 2026-06-01 21:07:40 -05:00
Author
Owner
Copy Link

@jherkenhoff commented on GitHub (May 31, 2026):

Same here after a fresh install

<!-- gh-comment-id:4587661879 --> @jherkenhoff commented on GitHub (May 31, 2026): Same here after a fresh install
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#511
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?