Too many certificates

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

The first five installations of Let's Encrypt claimed to be successful, but none of them actually worked. Now I am encountering this error regarding the limit. At the moment, Plesk still indicates that the website is secured with Let's Encrypt, but as you can see, this is not accurate.

My domain is:
pro2foundation.com

I ran this command:
Plesk install Let's Encrypt

It produced this output:
Could not issue an SSL/TLS certificate for pro2foundation.com
Details

Could not issue a Let's Encrypt SSL/TLS certificate for pro2foundation.com.

One of the Let's Encrypt rate limits has been exceeded for pro2foundation.com.

See the related Knowledge Base article for details.

Details

Invalid response from https://acme-v02.api.letsencrypt.org/acme/new-order.

Details:

Type: urn:ietf:params:acme:error:rateLimited

Status: 429

Detail: Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours: *.pro2foundation.com,pro2foundation.com, retry after 2024-07-16T06:00:59Z: see Duplicate Certificate Limit - Let's Encrypt

This text, along with the link it gave you, seems pretty clear. Did you need help with something?

3 Likes

Hey Dan,
The error message clearly states that there are too many requests. According to Plesk and Let's Encrypt, all the requests I submitted were successful, but when you visit the website, the SSL certificate isn’t functioning at all. Currently, I am unable to generate a new certificate, and I suspect that even if I do generate another one, I might encounter the same issue where it is indicated as working, but visiting the website reveals otherwise. Plesk now also shows that an SSL certificate has been installed, but as mentioned earlier, it is not working.

You've created five in the past week; you shouldn't need to create another one.

Indeed it isn't. Your site isn't using any of the Let's Encrypt certs it's obtained; it's instead using a self-signed cert. You should check with Plesk support, whoever that may be, to see how to actually use one of the certs you've obtained.

4 Likes

Indeed, there was a Let's Encrypt certificate installed before, but when I visited the website, it wasn't working, although adding a new domain name to the server and installing lets encrypt
works perfectly. However, this particular domain name doesn't seem to adopt it for some reason.

How can I currently bypass the 5-request limit, or how can I reapply for a certificate from Let's Encrypt? It indicates that I must wait 168 hours, but I doubt my client would appreciate having their website online without a certificate for that long :weary:

The error message (below) shows the next time success might be possible. So, a looks like about 32(?) hours from now. (time is UTC)

But, if you don't sort out your Plesk problem that won't work any better than your last 5 tries.

That link also suggests a work-around. Or, you can try using another ACME Certificate Authority. I don't know how you do that with Plesk personally. Again, that's a good question for your Plesk support.

3 Likes

Hey Mike,
I will open a ticket at the Plesk support, thanks! :slight_smile:

3 Likes

Where can I see how much longer it will be before I can apply for a new SSL?
I thought this was 168 hours but you said something about 32?

It was in the error message you posted. And I quoted it in my reply

3 Likes

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