Skip to content

Reduce the maximum number of retries from 99 to 9#416

Merged
icing merged 1 commit intoicing:masterfrom
mkauf:change_max_retries
Apr 20, 2026
Merged

Reduce the maximum number of retries from 99 to 9#416
icing merged 1 commit intoicing:masterfrom
mkauf:change_max_retries

Conversation

@mkauf
Copy link
Copy Markdown
Contributor

@mkauf mkauf commented Mar 20, 2026

Are 99 retries really necessary?

Feel free to decline this PR if you disagree - or use an even lower number if you want (3?).

@pizzi80
Copy link
Copy Markdown

pizzi80 commented Apr 20, 2026

sometimes I need more than 9 retries due to bad DNS synchronizations beetween providers and/or NIC problems ... my 2 cents ;)

@mkauf
Copy link
Copy Markdown
Contributor Author

mkauf commented Apr 20, 2026

@pizzi80 There are different types of retries. This PR changes the number of retries that are done immediately if a request to the ACME CA fails. If a certificate renewal operation fails, that operation is also retried, with a delay. This PR does not change that.

@mkauf mkauf force-pushed the change_max_retries branch from 6b0d2d0 to 16f1e50 Compare April 20, 2026 10:57
@pizzi80
Copy link
Copy Markdown

pizzi80 commented Apr 20, 2026

thanks for taking time to reply!

... my reply was only to represent a common situation
that sadly happens to me and probably other users ...

thanks for your work!!

@icing icing merged commit 1c37b47 into icing:master Apr 20, 2026
3 checks passed
@icing
Copy link
Copy Markdown
Owner

icing commented Apr 20, 2026

Thanks!

@mkauf mkauf deleted the change_max_retries branch April 20, 2026 11:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants