Edge Certificate - Rate Limit
Hello everyone! I have a Edge Certificate that has the error message available in the screenshot. The domain below has the same error, but is still accessible.
I wonder if the rate limit I reached is at the domain-level (all the other hostnames work fine) or at the hostname level.
The hostname with the "initializing" error is a hostname that has often changing IP, but I don't understand why this would cause a regeneration of the Edge Certificate.
I wonder if you have an idea about that?
I don't want to switch to Google Trust Services as I fear that the bulk regeneration of the domains will make me reach the rate-limit of Google Trust Services and make impossible the generation of certificates for my production environment.
Any insight would be appreciated, thanks a lot!
5 Replies
For what its worth, let's encrypt rate limits are generally stricter than Google's
They have both domain-based and hostname-based rate limits so the answer depends which one you hit specifically: https://letsencrypt.org/docs/rate-limits/
I think it would be the Duplicate Certificate limit, but I find odd, that the certificates needs to be regenerated on IP change
Do you know where i can find Google’s rate limit?
I don't think they publish per-domain limits?
Found the cause of the issue: Instead of just changing the entry, I was sometimes deleting in on terraform destroy, and recreating it was generating a new Edge Certificate
Ah