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.
My domain is:
I ran this command:
It produced this output:
Too many certificates already issued for
My web server is (include version):
The operating system my web server runs on is (include version):
CentOS Linux 7.9.2009
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):
Plesk Obsidian v18.0.45
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
A few weeks ago, a notification appeard on the dashboard of my server. It says, that the default host name will change on 01.08. and the old one will no longer be available anymore.
So I decided to update the hostname on Plesk which worked fine with a few issued I fixed by myself.
But unfortunately, I could'nt renew the SSL certificate for the Plesk url itself. Before it was an url like "https://ip----.ip.secureserver.net" (where *** is the ip of my server). The new url will look like "....host.secureserver.net".
When trying to renew the certificate, it'll give me the following error:
Type: urn:ietf:params:acme:error:rateLimited Status 429 Detail: Error creating new order :: too many certificates already issued for secureserver.net: see https://letsencrypt.org/docs/rate-limits
Of course I know the meaning of this error, but I'm one of maybe thousands or ten-thoussands of customers that uses ....host.secureserver.net.
Any ideas how to fix that issue? Thank you.