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 #587

New Issue
Open
opened 2026-06-04 23:27:24 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-06-04 23:27:24 -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-04 23:27:27 -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
GiteaMirror commented 2026-06-04 23:27:28 -05:00
Author
Owner
Copy Link

@Scarpy19 commented on GitHub (Jun 4, 2026):

I encountered the same 400 Bad Request error when reporting peer bandwidth after updating the Gerbil package in my Docker setup.

I have:

  • Two separate docker-compose.yml stacks: one for Pangolin and another for a Arcane.
  • Both stacks share an external Docker network.

To fix it i stopped both compose stacks, first arcane, then pangonil. Started the Pangolin stack first and waited for it to fully initialize. Then started the Arcane stack.

After this, the 400 Bad Request errors stopped and everythin started working correctly.

I know you did a fresh install but check another network services around there

<!-- gh-comment-id:4625349205 --> @Scarpy19 commented on GitHub (Jun 4, 2026): I encountered the same `400 Bad Request` error when reporting peer bandwidth after updating the Gerbil package in my Docker setup. I have: - Two separate `docker-compose.yml` stacks: one for **Pangolin** and another for a **Arcane**. - Both stacks share an external Docker network. To fix it i stopped both compose stacks, first arcane, then pangonil. Started the **Pangolin** stack first and waited for it to fully initialize. Then started the **Arcane** stack. After this, the `400 Bad Request` errors stopped and everythin started working correctly. I know you did a fresh install but check another network services around there
GiteaMirror commented 2026-06-04 23:27:29 -05:00
Author
Owner
Copy Link

@zer0ish commented on GitHub (Jun 4, 2026):

I encountered the same 400 Bad Request error when reporting peer bandwidth after updating the Gerbil package in my Docker setup.

I have:

  • Two separate docker-compose.yml stacks: one for Pangolin and another for a Arcane.
  • Both stacks share an external Docker network.

To fix it i stopped both compose stacks, first arcane, then pangonil. Started the Pangolin stack first and waited for it to fully initialize. Then started the Arcane stack.

After this, the 400 Bad Request errors stopped and everythin started working correctly.

I know you did a fresh install but check another network services around there

By Arcane, do you mean the GetArcane docker manager like Portainer? I do use it.
I did your steps and the issue persists.

Girbil just got an update today, but it didn't address this issue.

<!-- gh-comment-id:4625550497 --> @zer0ish commented on GitHub (Jun 4, 2026): > I encountered the same `400 Bad Request` error when reporting peer bandwidth after updating the Gerbil package in my Docker setup. > > I have: > > * Two separate `docker-compose.yml` stacks: one for **Pangolin** and another for a **Arcane**. > * Both stacks share an external Docker network. > > To fix it i stopped both compose stacks, first arcane, then pangonil. Started the **Pangolin** stack first and waited for it to fully initialize. Then started the **Arcane** stack. > > After this, the `400 Bad Request` errors stopped and everythin started working correctly. > > I know you did a fresh install but check another network services around there By Arcane, do you mean the GetArcane docker manager like Portainer? I do use it. I did your steps and the issue persists. Girbil just got an update today, but it didn't address this issue.
GiteaMirror commented 2026-06-04 23:27:30 -05:00
Author
Owner
Copy Link

@Scarpy19 commented on GitHub (Jun 4, 2026):

Yes, i mean Arcane. I tested again and shutting down first Arcane completely and waiting for pangolin to be up address the issue. Doing it in another order gives me the error 400 bad request.

<!-- gh-comment-id:4626366096 --> @Scarpy19 commented on GitHub (Jun 4, 2026): Yes, i mean [Arcane](https://github.com/getarcaneapp/arcane). I tested again and shutting down first Arcane completely and waiting for pangolin to be up address the issue. Doing it in another order gives me the error 400 bad request.
GiteaMirror commented 2026-06-04 23:27:31 -05:00
Author
Owner
Copy Link

@zer0ish commented on GitHub (Jun 4, 2026):

Yeah didn't work for me. A solution via update would be better. Having to do those steps every time I update or reboot is worst then just having the spam msg I don't really see unless I open the log.

<!-- gh-comment-id:4626619943 --> @zer0ish commented on GitHub (Jun 4, 2026): Yeah didn't work for me. A solution via update would be better. Having to do those steps every time I update or reboot is worst then just having the spam msg I don't really see unless I open the log.
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#587
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?