Too many certificates already issued for exact set of domains

Following the update of our OVH host, we had to renew our certificate.
However, we have reached the validation limit of 5 per week by mistake on our part.
We have blocked customers, is it possible to lift this restriction, otherwise we have to wait another 5 days.
Please excuse us for our mishandling.


Mon nom de domaine est :

Hi @CailBzd, and welcome to the LE community forum :slight_smile:


Where are the five issued certs?

If you provide more information, we might be able to help more:

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:

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is:

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


What was the mistake? Has it been corrected yet? Do you need help correcting it?

There is a workaround, but everyone here wants to ensure you have fixed the problem first – and will be happy to help you do that.


In case you have not yet fixed the problem, there is a "test" / "staging" environment for which to do all the testing and preventing such experimenting with the production system and this outcome.


We haved an error of saving certificates files on our kebernetes pvc. It's corrected now.

My domain is : |

Now that we know, we use the environment "test".


We had several kubernetes updates to do. Our mistake was to request a certificate renewal from each of them... So we were stuck on the fifth request...
We applied a patch in the kubernetes PVC

1 Like

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