Page MenuHomePhabricator

Evaluate requesting a rate limit change from Letsencrypt
Closed, ResolvedPublic

Description

This is a ticket to discuss whether it makes sense for us to fill out this form and request a rate limit change from Letsencrypt for Wikimedia.

https://docs.google.com/forms/d/e/1FAIpQLSfg56b_wLmUN7n-WWhbwReE11YoHXs_fpJyZcEjDaR69Q-kJQ/viewform?c=0&w=1

https://letsencrypt.org/docs/rate-limits/

14:15 < Krinkle> "If you are a large hosting provider or organization working on a Let’s Encrypt integration, we have a rate limiting form that"
14:15 < Krinkle> Sounds like us :)

This came up in the context of hitting the rate limit after a reinstall of gerrit-slave.wm.org but this isn't for a specific case but to figure out if it makes sense for us as an org in general.

Event Timeline

Dzahn triaged this task as Low priority.Sep 27 2017, 7:47 PM
Dzahn added subscribers: Krinkle, BBlack.
BBlack claimed this task.

So far in all the cases I've seen, when we've hit the ratelimit it's been a useful signal to tell us we've got broken software and/or processes. I'd say let's leave this alone unless we find a legitimate need for raising the limits.

Yep, at the time of writing this ticket we weren't aware that the rate-limiting issue was ultimately caused by a software issue specific to stretch machines (openssl output format change broke acme-setup). This is now fixed, so the issue is moot. Thank you Brandon.