Rate limit restriction when no requests made yet


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. https://crt.sh/?q=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: cheshiremothcharts.com

I ran this command: ./certbot-auto --debug -v --server https://acme-v01.api.letsencrypt.org/directory certonly -d cheshiremothcharts.com

It produced this output: Error: urn:acme:error:rateLimited :: Error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new cert :: too many certificates already issued for: cheshiremothcharts.com: see https://letsencrypt.org/docs/rate-limits/

My web server is (include version): Apache/2.2.34 (Unix)

The operating system my web server runs on is (include version): Amazon Linux AMI 2018.03

My hosting provider, if applicable, is: Amazon

I can login to a root shell on my machine (yes or no, or I don’t know): Yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No

This is the first time I’ve requested a certificate for this domain. The only previous Let’s Encrypt certificate request I’ve made is for another domain hosted on the same server (consonant.co.uk), which was successful.

https://crt.sh/ indicates there are no existing certificates for this domain.

I’ve looked for similar topics but haven’t found one addressing this issue.



There are no certificates for that exact name, but there are lots of certificates for subdomains of cheshiremothcharts.com:


When you have an afraid.org shared domain – private or not – other people can create subdomains, and they did.

See also:


Oh dear. Thanks for explaining this, and the extremely quick response! I would never have figured this out. Time to say goodbye to afraid.org I guess.



Migrated to Cloudflare now. Thanks again.