[GH-ISSUE #143] Client disconnects due to a wrong retry logic #322

Closed
opened 2026-08-05 00:38:13 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @braginini on GitHub (Oct 31, 2021).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/143

Originally assigned to: @braginini on GitHub.

Wiretrustee client has a Management server connection retry logic with a MaxElapsedTime = 3 days.
The goal of this is to prevent infinite retrying of the client app if the issue is permanent (e.g. client was excluded from the network)

What happens is that on a single unsuccessful connection to the management system the retry mechanism starts the 3 days timer.
Even if the 2nd attempt was successful, after 3 days in case there was a connection error the backoff mechanism quits retrying.

There should be some logic resetting the backoff mechanism on successful connection to Management.

Originally created by @braginini on GitHub (Oct 31, 2021). Original GitHub issue: https://github.com/netbirdio/netbird/issues/143 Originally assigned to: @braginini on GitHub. Wiretrustee client has a Management server connection retry logic with a MaxElapsedTime = 3 days. The goal of this is to prevent infinite retrying of the client app if the issue is permanent (e.g. client was excluded from the network) What happens is that on a single unsuccessful connection to the management system the retry mechanism starts the 3 days timer. Even if the 2nd attempt was successful, after 3 days in case there was a connection error the backoff mechanism quits retrying. There should be some logic resetting the backoff mechanism on successful connection to Management.
saavagebueno added the bug label 2026-08-05 00:38:13 -04:00
Sign in to join this conversation.
No Label bug
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#322