This domain agile-sportswear.com shows rate limit. Can someone from the team if possible can remove rate limit please. Its urgent
Which rate limit, and why?
(Don't get your hopes up, it won't be reset. Most you can hope is a more generous rate limit, but you have to read the documentation on that)
6 Likes
I think someone from the team can do that. Rate limit happened with purely my mistake and DNS issue 
There are several different rate limits.
Your domain is using a completely wrong cert right now so I don't know this is your biggest issue. You have various valid certs for that domain
4 Likes
You need to be more specific.
Please provide the exact error message that led you to think you are being rate limited.
Let's Debug doesn't show any problems:
Let's Debug (letsdebug.net)
4 Likes
Its shared siteground hosting sir. There is no log just rate-limit message displayed.
Thanks I can now issue certificate. Can close the topic
Your domain name is not ratelimited. The rate limit is on Siteground's account or something else they messed up.
~$ podman run -i docker.io/certbot/certbot certonly --standalone --register-unsafely-without-email --agree-tos -d agile-sportswear.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Account registered.
Requesting a certificate for agile-sportswear.com
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: agile-sportswear.com
Type: unauthorized
Detail: 34.174.232.245: Invalid response from http://agile-sportswear.com/.well-known/acme-challenge/nTqqOcgHion2BqvPgSBKuqRybVO_-CiQW2o1dga5XnM: 404
Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
3 Likes
I'm not sure what you meant, but if you meant that someone from the Let's Encrypt team can remove rate limits: no, that's (in practice) not possible. Let's Encrypt is fully automated and if the server software says you're rate limited, that's just a fact. In theory everything is possible of course, but it would probably require manually messing in the production database and that's not something Let's Encrypt does.
A good way to avoid running into rate limits is using the staging environment for testing and only after your testing succeeds, change to the production environment.
It could be the "too many failed authz" rate limit, which is account specific
5 Likes
Also "too many certs for this exact set of names" (assuming crtsh is again backlogged)
4 Likes
Other CT log aggrerators (e.g. Entrust Certificate Search - Entrust, Inc.) show just 2 LE certs and 1 Sectigo cert.
1 Like
Ok, since you asked censys.io shows below. crt.sh does not have the get subdomain cert from Aug8 as well as missing today's LE certs
4 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.