Failed to report peer bandwidth: API returned non-OK status: 400 Bad Request

[zer0ish]

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

[jherkenhoff]

Same here after a fresh install

[Scarpy19]

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

[zer0ish]

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.

[Scarpy19]

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.

[zer0ish]

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.

[CAPTAlNHOWDY]

Same issue here. Pangolin 1.20.0, Gerbil 1.4.2, Trafic 3.7.7