It produced this output: An unexpected error occurred: There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: cyprien-wacogne.com: see https://letsencrypt.org/docs/rate-limits/
The operating system my web server runs on is (include version): nginx
My hosting provider, if applicable, is: Scaleway
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): With PPA
I’ve tried with LE_FIND_PENDING_AUTHZ too, but no solution
Analysing File: letsencrypt.log
Found: no matches for Success Regex
Analyzing For Pending Authz
Found : 0 Authz in file
Analysing File: LE_FIND_PENDING_AUTHZ.py
Found matches for Success Regex
Not Analyzing For Pending Authz
No offence intended, but that doesn't sound very professional. I'm sure as a professional, you've got backups? Also, the certificates aren't really the issue, they are publically available (on for example crt.sh), the private keys are important.
In any case, the rate limits are sliding windows. With this case, you can issue a new certificate with the same set of domains again 7 days after the issuance of the 5th newest certificate.
As all of the recent certs have been issued yesterday, you've got to wait 6 more days or use the trick mentioned by @9peppe.
I don’t know what you mean. crt.sh is just a site with a searchable list of certificates from Certificate Logs. If you don’t have the private keys any longer, you can’t use the previous certificates issued, so crt.sh won’t help you.