Artificial rate limite to avoid incorrect automation #18

New Issue

2026-10-01T01:56:59+02:00

Benjamin_Loison commented

2026-10-01 01:56:59 +02:00

I completely read https://letsencrypt.org/docs/rate-limits/#new-certificates-per-exact-set-of-identifiers.

Well as mentioned I was trying to debug, making a parameter to force proceeding for debugging would be cleaner than specifying an ad-hoc domain, in my case server0.lemnoslife.com in addition to wanted gitea.lemnoslife.com.

I completely read https://letsencrypt.org/docs/rate-limits/#new-certificates-per-exact-set-of-identifiers. Well as mentioned I was trying to debug, making a parameter to force proceeding for debugging would be cleaner than specifying an ad-hoc domain, in my case `server0.lemnoslife.com` in addition to wanted `gitea.lemnoslife.com`.

Benjamin_Loison commented

2026-10-01 01:57:29 +02:00

https://letsencrypt.org/docs/rate-limits/#new-certificates-per-exact-set-of-identifiers

Related to #17.

https://letsencrypt.org/docs/rate-limits/#new-certificates-per-exact-set-of-identifiers Related to #17.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Benjamin_Loison/certbot#18