jsha
January 12, 2016, 11:48pm
1
Continuing the discussion from Public beta rate limits :
Here is the problem detail response:
{"type":"urn:acme:error:rateLimited","detail":"Error creating new cert :: Too many certificates already issued for: xxxxxx.tld","status":429}
What's interesting though, is that this message must not be surfacing all the details of the limit that was hit because I only get this error when the test runs on my CI server, but when I run it from my development box (with the same domain), it still works fine. So I suspect this must be some limit per IP address or address range perhaps?
Let me know if you need the specific domain in order to troubleshoot or dig into it.
Could it be that your CI box is hitting staging, but your dev box is hitting prod?
1 Like
ebekker
January 13, 2016, 12:05am
2
Just confirmed, the CI server is talking to staging, for example, here is the Identifier status URI for the most recent run (just moments ago):
https://acme-staging.api.letsencrypt.org/acme/authz/y2zQ92UptY5ApMNMG6hIfDFlpgA6_NcEGblnnU3hshU
I also did go through the most recent dozen or so CI runs and also confirmed that they were all built on the same build box, so it would have presented the same same IP address to LE each time.
Well it took a little while, but now Iām hitting the same rate limit in dev as well as the CI server.