Let's Encrypt Rate Limit Reached: Wait or Use Staging
Limits.
Let's Encrypt limits how many certificates you can request in a given period. If you hit a limit, requests are refused until the window resets. The limits are there to prevent abuse, and they are rarely a problem if you avoid repeated retries.
Step 1: Read the exact error

It names the limit, such as too many certificates for a registered domain, too many failed validations or a duplicate certificate limit.
Step 2: Stop retrying

Repeated attempts during a failed-validation limit make it last longer.
Step 3: Find why the requests failed

Most limit problems begin with a failed validation: the domain does not point to the server, a firewall blocks the validation file, or a redirect rule breaks it.
Step 4: Wait for the limit to reset

Most limits reset after an hour, a day or a week. The error message or the Let's Encrypt documentation gives the exact window.
Step 5: Use the staging server for tests

Add the --staging option (or the staging endpoint) while you test your setup. It has much higher limits and issues untrusted test certificates.
Step 6: Reduce requests

Combine names in one certificate, do not delete and recreate certificates, and renew only when needed.
Step 7: On shared hosting

Ask your host to check the certificate, because they may run the requests for you.
Still stuck?
If these steps do not solve it, we fix it for you for a flat $99. Full refund if we do not solve it within 7 days.
Related guides
- What Is an SSL Certificate Authority and Chain of Trust
- What Is a Domain Registrar vs Web Host vs DNS Host
- What Does 'Not Secure' Mean in the Browser?
- Too Many Redirects With Cloudflare: Flexible SSL Loop Fix