Maximal certificate requests reached for this domain name

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: N/A

It produced this output: N/A

My web server is (include version): Synology Web Station

The operating system my web server runs on is (include version): N/A

My hosting provider, if applicable, is: Self

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

I made two mistakes when creating a new Let's Encrypt certificate and deleted both. I discovered my error but on the third attempt ran into the message "Maximal certificate requests reached for this domain name." Reading the forums the limit will reset every week. Does this mean I can try again to issue the certificate on Monday? Or is it possible that you could reset for me? Any help greatly appreciated!

That is not the exact error message from Let's Encrypt for this situation.

I see you have been getting certs from Sectigo. Could it be their error message?


Thank you for your response! I have moved the hosting from ipower to my own Synology NAS. I assume "Sectigo" is from ipower which I no longer want to use. Instead I'm using Synology and creating my own certificate. When I try to create a new certificate I'm now getting the message " "Maximal certificate requests reached for this domain name." My error was I forgot to add both of these domains:
FOR: sfoyama; www.sfoyama. I only added previously and that was my mistake.

It does look like you've gotten a bunch of duplicative certificates for the same names from Let's Encrypt. If you hit the duplicate certificate rate limit, you will have to wait 7 days since the issuance of the original certificate before you can issue any more.


Thank you schoen. OK, thank you very much. I can wait the seven days and am very relieved that it will reset. Thanks again for your help!

1 Like

I think that is the 1 hour limit [for failed attempts].
What is the name you are trying to use?

3 Likes It wasn't a failed attempt, the certificate issued but for the "Subject Alternative Name" (For) I need both the domain and subdomain (www and no www) included. That is what I neglected to do and looks like I now need to wait 7 days to try again.

There is a Let's Encrypt limit of 5 certs with the identical names (SAN) per week.

You have gotten 5 with your apex and www names in the past day (see here)

Why do you think the certs you've gotten only include your apex name?

As I noted earlier, the Let's Encrypt error message for this rate limit is described below.
It looks like Synology may be changing that error message or perhaps doing a check on its own. I wish they wouldn't do that because there are various rate limits and it makes it harder to help.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.