Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ratelimits documentation for Automatic Pausing #1785

Merged
merged 1 commit into from
Dec 5, 2024

Conversation

beautifulentropy
Copy link
Member

@beautifulentropy beautifulentropy commented Dec 5, 2024

Add documentation for the limits used to enforce automatic pausing of zombie clients: https://community.letsencrypt.org/t/automatic-pausing-of-zombie-clients/229642

@beautifulentropy beautifulentropy marked this pull request as draft December 5, 2024 18:32
@beautifulentropy beautifulentropy force-pushed the pausing-limits branch 4 times, most recently from 78bdbc3 to cbb02fb Compare December 5, 2024 18:47
@beautifulentropy beautifulentropy marked this pull request as ready for review December 5, 2024 18:49
@beautifulentropy beautifulentropy merged commit f99a3b5 into main Dec 5, 2024
5 checks passed
@beautifulentropy beautifulentropy deleted the pausing-limits branch December 5, 2024 20:12
requesting new certificates for that hostname. Each time the subscriber attempts
to request a certificate they will receive an error containing a link to our
Self-Service Portal where they can unpause issuance for the paused hostname and
up to 50,000 additional paused hostnames associated with their account.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe there is an off‐by‐one glitch here? If Boulder unpauses up to 50,000 identifiers per request, shouldn’t it be ‘the paused hostname and up to 49,999 additional paused hostnames’?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, fun! Yeah, I think you're correct here.

bdaehlie pushed a commit that referenced this pull request Jan 9, 2025
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.

4 participants