Is my ip blocked?

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.

Now I try with other domain, but is my ip blocked? I am very new to domain and having too much pressure on me due to prod issue. Would you kindly check if my ip is blocked?
My domain is:
I ran this command:
certbot certonly --manual --email --preferred-challenges dns
--server --agree-tos
-d ',*'

It produced this output:
too many attempts- wait 168 hours.
My web server is (include version):

The operating system my web server runs on is (include version):
ubuntu 20.04
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):
certbot certonly --manual --email --preferred-challenges dns
--server --agree-tos
-d ',*'

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

That sounds like a misquote - try "copy/paste" instead of typing.
If there were too many attempts, then the wait time would be only an hour.
If it states 168 hours, then there have been too many certs issued recently for that set of names.

In any case, you should do all your testing [yes, when this fail and continue to fail we call that testing] on the staging environment [not on the production environment].


And to answer your question:
"Is my ip blocked?"
No; The response shown proves it is being responded to [which implies that your IP wasn't blocked].

What happened to the recently issued certs?:

What shows?:
certbot certificates


To answer your question directly: no, your IP address is not blocked.

To answer your question more broadly: yes, you're "blocked" in the sense that you're prohibited to issue more duplicate certificates as you're abusing the Let's Encrypt service by throwing away perfectly fine certificates. Or you're not using them anyway.


@merve Please see


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