dry-run works flawlessly
./certbot-auto renew --dry-run Saving debug log to /var/log/letsencrypt/letsencrypt.log Processing /etc/letsencrypt/renewal/www.domain.com.conf Cert is due for renewal, auto-renewing... Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org Renewing an existing certificate Performing the following challenges: tls-sni-01 challenge for www.domain.com tls-sni-01 challenge for sub1.domain.com tls-sni-01 challenge for domain.com tls-sni-01 challenge for sub2.domain.com Waiting for verification... Cleaning up challenges Generating key (2048 bits): /etc/letsencrypt/keys/0009_key-certbot.pem Creating CSR: /etc/letsencrypt/csr/0009_csr-certbot.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/www.domain.com/fullchain.pem (success) ** DRY RUN: simulating 'certbot renew' close to cert expiry ** (The test certificates above have not been saved.)
The cron log says it’s running just fine… but it doesn’t upgrade the certificates. I want this cron’d so I don’t have to run it manually every time they are about to expire.
Dec 14 21:59:01 CRON: (root) CMD (/usr/sbin/certbot-auto renew --quiet --no-self-upgrade )
Why can’t you issue these certificates for a normal amount of time instead of just 3 months… That would save a lot of trouble.
My certs expire dec 26, isn’t this command supposed to update them automatically?