Can you remove us from blacklist , so we can receive new certificates.
Can you tell us which information we need to provide for this issue to be resolved.
You aren't going to be on a blocklist. You most likely exceeded rate limits and will have to wait until they expire.
If you still have questions, 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:
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):
4 Likes
Clients that have hit rate limits cannot be removed on an individual basis. Please use the staging environment for testing to prevent these kind of errors.
Please don't re-issue duplicate certificates, but simply use the first one you've gotten issued. Every certificate issuance costs Let's Encrypt in the sense of performance/equipment. Re-issuing duplicate certificates on the production environment without a good reason is abusive and thus there are rate limits in place to prevent this abuse.
3 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.