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: getfotge.io
I ran this command:
certbot-auto certonly --agree-tos --webroot --webroot-path ‘/tmp/’ --force-renewal --non-interactive -d
It produced this output:
An unexpected error occurred:
There were too many requests of a given type :: Error creating new cert :: too many certificates already issued for: getforge.io
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):no
The main limit is Certificates per Registered Domain, (20 per week). A registered domain is, generally speaking, the part of the domain you purchased from your domain name registrar. For instance, in the name www.example.com, the registered domain is example.com. In new.blog.example.co.uk, the registered domain is example.co.uk. We use the Public Suffix List to calculate the registered domain.
It appears that some of those must be renewals, based on the number issued in one day. Scorpius, please note that renewals, while exempted from the rate limit, still count against it. As such, you’ll want to perform any new issuances before performing renewals. This takes some careful planning, and I know Let’s Encrypt is working on making this more pleasant, but that’s where it stands now.