Guides › HTML / PHP sites › Domain, DNS & SSL

Let's Encrypt Rate Limit Reached: Wait or Use Staging

Limits.

Reference guide. This guide is written from established practice and the official documentation of the tools involved. We have not yet tested every step on a live demo site. Back up your site before you change anything.
Domain, DNS and SSL

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.

1Read the exact error2Stop retrying3Find why the requests failed4Wait for the limit to reset5Use the staging server for tests6Reduce requests7On shared hostingFixed? Test the site. If not, get help.
The steps in order. Work down the list and stop when the problem is solved.

Step 1: Read the exact error

Illustration for 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

Illustration for Step 2: Stop retrying

Repeated attempts during a failed-validation limit make it last longer.

Step 3: Find why the requests failed

Illustration for 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

Illustration for 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

Illustration for 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

Illustration for 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

Illustration for 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

Did this solve it? If not, email hello@sitefixlab.org with the exact error text and we will look into it. Try the problem finder.

Last updated 2026-11-22.