Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Attempting to renew cert (malamut.es) from /etc/letsencrypt/renewal/malamut.es.conf produced an unexpected error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/malamut.es/fullchain.pem (failure)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/malamut.es/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
My web server is (include version): Apache version 2.2.15
The operating system my web server runs on is (include version):
CentOS 6
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
Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for malamut.es
Waiting for verification…
Cleaning up challenges
new certificate deployed with reload of apache server; fullchain is
/etc/letsencrypt/live/malamut.es/fullchain.pem
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)
Congratulations, all renewals succeeded. The following certs have been renewed:
/etc/letsencrypt/live/malamut.es/fullchain.pem (success)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)
the contents of /etc/letsencrypt/renewal/malamut.es.conf are:
Do you have any other domains on that server being managed by Certbot? If they were failing, they could have “eaten up” the failed authorization rate limit before malamut.es had a chance to run.
Wait out the rate limit window (60 minutes) and try again without --dry-run. If you still get an error (and it isn’t the rateLimited error), post back.
Alternatively if you can find the right log file in /var/log/letsencrypt/ before the rate limits occurred, that would also reveal the issue.
Do you have a cron job setup for certbot-auto? What does it look like?
Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Performing the following challenges:
tls-sni-01 challenge for malamut.es
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (malamut.es) from /etc/letsencrypt/renewal/malamut.es.conf produced an unexpected error: Failed authorization procedure. malamut.es (tls-sni-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Incorrect validation certificate for tls-sni-01 challenge. Requested 1e0d08e268fdd842630c71397284485c.04c0ed968224109d7dd6f3131bcfbc7d.acme.invalid from 209.153.127.192:443. Received 2 certificate(s), first certificate had names “malamut.es”. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/malamut.es/fullchain.pem (failure)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/malamut.es/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
The following errors were reported by the server:
Domain: malamut.es
Type: unauthorized
Detail: Incorrect validation certificate for tls-sni-01 challenge.
Requested
1e0d08e268fdd842630c71397284485c.04c0ed968224109d7dd6f3131bcfbc7d.acme.invalid
from 209.153.127.192:443. Received 2 certificate(s), first
certificate had names “malamut.es”
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
–
This is the pastebin link for the log file : https://pastebin.com/PrufuPhW