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: aperturemaps.com
I ran this command: certbot renew
It produced this output:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/www.aperturemaps.com.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate for www.aperturemaps.com
Attempting to renew cert (www.aperturemaps.com) from /etc/letsencrypt/renewal/www.aperturemaps.com.conf produced an unexpected error: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: www.aperturemaps.com: see https://letsencrypt.org/docs/rate-limits/. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/www.aperturemaps.com/fullchain.pem (failure)
My web server is (include version): apache2
The operating system my web server runs on is (include version): Linux Mint 19.2 (Ubuntu 18.04 LTS)
My hosting provider, if applicable, is: NA
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
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you're using Certbot): 1.10.1
Hello all,
I went to renew my certificate this morning. The first time I did so, I got several parse errors from invalid .conf files (probably left around from not setting things up right the first time, definitely my fault here, I've deleted them now) and a renew failure because there was a file in the way:
File exists: '/etc/letsencrypt/archive/www.aperturemaps.com/privkey2.pem'. Skipping.
I've renamed the file that was already in the way. Now, when I go run the certbot renew
it tells me that I've hit my rate limit, and checking crt.sh (https://crt.sh/?q=www.aperturemaps.com) I can see that multiple certificates were generated this morning (as well, it would appear, as many over the last couple weeks -- autorenewals, it appears, and again, operator error on my part not trying to figure out renewal ahead of time).
From the rate limits page (https://letsencrypt.org/docs/rate-limits/) it appears that I'm out of luck for the next week, and then I'll need to be more careful and make sure I don't consume all of my renewals in a single go. Is this the case, or can I somehow retrieve the certificate that was generated the first time but couldn't be saved to use that?
Thanks!