I got the first email on Jan 27th, upgraded the client and run the dry-run which succeeded.
Today I got a new notification email claiming I still had a renewal on 2019-02-09 using ACME TLS-SNI-01.
Not sure who is lying here…
My domain is:utopia14.org
I ran this command:sudo certbot renew --dry-run
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/polny-shkaf.utopia14.org.conf
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator apache, Installer apache
Starting new HTTPS connection (1): acme-staging-v02.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for polny-shkaf.utopia14.org
http-01 challenge for www.utopia14.org
Waiting for verification…
Cleaning up challenges
Resetting dropped connection: acme-staging-v02.api.letsencrypt.org
new certificate deployed with reload of apache server; fullchain is
/etc/letsencrypt/live/polny-shkaf.utopia14.org/fullchain.pem
Processing /etc/letsencrypt/renewal/utopia14.org.conf
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator apache, Installer apache
Starting new HTTPS connection (1): acme-staging-v02.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for polny-shkaf.utopia14.org
http-01 challenge for utopia14.org
http-01 challenge for www.utopia14.org
Waiting for verification…
Cleaning up challenges
Resetting dropped connection: acme-staging-v02.api.letsencrypt.org
new certificate deployed with reload of apache server; fullchain is
/etc/letsencrypt/live/utopia14.org/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/polny-shkaf.utopia14.org/fullchain.pem (success)
/etc/letsencrypt/live/utopia14.org/fullchain.pem (success)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)
My web server is (include version):
httpd-2.4.6-88.el7.centos.x86_64
The operating system my web server runs on is (include version):
CentOS Linux release 7.6.1810 (Core)
My hosting provider, if applicable, is:
linode
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): certbot 0.29.1