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.
I was trying to produce a new certificate for domain ilc.dev.g9telecom.pt. I tested on the last Friday, yesterday and today, with the same results.
I ran this command, as root in a bash shell:
certbot-auto --redirect --uir --apache -d skeleton.dev.g9telecom.pt
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator apache, Installer apache Obtaining a new certificate Performing the following challenges: http-01 challenge for skeleton.dev.g9telecom.pt Waiting for verification... Cleaning up challenges An unexpected error occurred: There were too many requests of a given type :: Error finalizing order :: too many certificates already issued for: g9telecom.pt: see https://letsencrypt.org/docs/rate-limits/ Please see the logfiles in /var/log/letsencrypt for more details.
When checking on crt.sh, at https://crt.sh/?q=%.g9telecom.pt I confirmed that only 1 certificate was issued in the past 7 days, and it was a renovation, and so I’m not even close to the 20 certificates per week limit.
I was able to issue the certificate with the staging server.
This is a virtual machine, it was cloned and I’ve tried on Friday to issue a certificate for another hostname in the same domain, which failed. Could this be related to use the exact same account in another host? Don’t think so, but after issuing dozens of certificates in the past years, this is the first time that I’ve got this error without a reason.
I’m running a Apache/2.4.6 on a CentOS Linux release 7.4.1708 (Core).