Type :: Error creating new order :: too many certificates already issued for exact set of domains:


Am getting the below error while publishing my site in Carrd.co. Contacted support and they reverted that LetsEncrypt is generating an error "type :: Error creating new order :: too many certificates already issued for exact set of domains: " and it should be reverted in 2 days. Its more than 2 days now and am still not able to publish. Carrd.co confirmed its the same error.

Can anyone help me with this.

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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: www.sasdesign.in

I ran this command: Published the site

It produced this output: type :: Error creating new order :: too many certificates already issued for exact set of domains:

My web server is (include version):

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

My hosting provider, if applicable, is: carrd.co

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):

1 Like

Welcome to the Let’s Encrypt Community, Ajay :slightly_smiling_face:

You can see the certificates you’ve generated here:

You can only generate 5 certificates with identical domains in a rolling 7 day period. This means that September 19 will be when you can generate another certificate. Any idea what happened to the 5 certificates you already generated?

1 Like

Thanks for the quick reply Griffin.

Am not well versed with it, but carrd.co were issuing the certificates. We published our site not knowing of this limitation. Do we need a new certificate every time we publish a site?

1 Like

No. A certificate remains usable regardless of the content changing. Recovering a certificate is easy. Recovering the private key for the certificate is practically impossible. Are the certificates (and private keys) still on the server?

Hi Griffin,

Let me check with Carrd support and revert on this. Also, is there anything else i can do to have the SSL enabled earlier.


1 Like

Possibly. It’s best to check to see if the certificates and private keys are still there though. If they are, it should be simple to install one. It looks like you just got a Cloudflare certificate installed that won’t expire for a year, so at least you’re covered. :slightly_smiling_face:

Hi Griffin,

Yes, post your reply realized that the certificate will be renewed on 19 Sep. Was earlier in the impression that it will be done in 2 days so was waiting for it to complete.

Would you know if i have to publish the site again or the last published site will be routed through cloudflare.


1 Like

Your certificate should be independent of your content, so publishing should not affect your certificate (and vice versa) unless carrd is doing something strange. I recommend SECURELY backing up your active certificate and private key just to make sure you have them on hand.

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