Not able to renew


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: Manual Verification

It produced this output:
Certificate signature failed. If you supplied your own CSR make sure the domains on it match what you put on SSLForFree. If there is a rate limiting error at the end of this paragraph certificates per Domain is currently 5 per 7 days. Try asking Lets Encrypt to increase the limit or wait 7 days. Rate limits should increase in the near future. { “type”: “urn:ietf:params:acme:error:rateLimited”, “detail”: “Error finalizing order :: too many certificates already issued for exact set of domains:, see”, “status”: 429 }

My web server is (include version): Apache 2.4 with CWP

The operating system my web server runs on is (include version): Apache

My hosting provider, if applicable, is:

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

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


Why not use one of the 10 other certificates you issued this week?

Rate Limit Current Status Domain
50 Certificates per Registered Domain per week OK (10 / 50 this week.)
5 Duplicate Certificates per week Limit exceeded. Next issuable at 2018-12-22T12:28:17.000Z,
5 Duplicate Certificates per week Limit exceeded. Next issuable at 2018-12-22T12:28:12.000Z

Summary generated at .


I never received the certificates on the page. It always gave an error. So I tried many times. Failed! So I took help of this. I have the certificate now, where is the private key!


Do you remember what the original error was? The certificates were created just fine.

Unfortunately if you have lost your private keys and you cannot retrieve them using, then they are gone forever.

At this time, you have two choices:

  1. Wait 5 days for the rate limit to elapse, or
  2. Add a third name to the certificate, so it is not considered a “duplicate”. For example In this case, I would suggest using a site like ZeroSSL to create the certificate instead, which may not suffer from whatever problem you ran into.


I tried ZeroSSL, which ran into the same error message. I will wait for 5 days from today. Then try ZeroSSL and also set up a cron job later, to avoid such mistakes. Thanks.


If I wasn’t clear, if you want to issue a new certificate now (and not get that error), you’d need to do it for a different set of domains.

If you’re happy to use DNS validation, you can tell ZeroSSL to give you a certificate for: *


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