It produced this output: An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: *.destroyernet.com: see https://letsencrypt.org/docs/rate-limits/
My web server is (include version): Apache 2.4.6
The operating system my web server runs on is (include version): CentOS 7
My hosting provider, if applicable, is:
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): 0.39.0
ETA: I waited the customary week after initially getting this error but it made no difference. The last cert crt.sh shows is the one that just expired (that I was trying to renew).
From the below link, you can see that you’ve got 5 certificates issued the past 6 days, and the next one you can get on 2019-12-14 01:58:02 (Not sure what timezone it’s on, think it’s my local timezone)
I see. That explains a lot. I’m curious as to why I have so many when they don’t actually go to anything; I did a number of attempted renewals but got this error:
Attempting to renew cert (destroyernet.com) from /etc/letsencrypt/renewal/destroyernet.com.
conf produced an unexpected error: The manual plugin is not working; there may be problems
with your existing configuration.
The error was: PluginError(‘An authentication script must be provided with --manual-auth-ho
ok when using the manual plugin non-interactively.’,). Skipping.
All renewal attempts failed. The following certs could not be renewed:
…so I then learned that you can’t do an autorenew with wildcards; you need to use the --manual certonly method you used to get the initial wildcard cert. So each of these generated a cert even though it said it failed?