CRON[3889]: Authentication token is no longer valid; new one required

cerbot-auto renew --dry-run works just fine with no errors. But when I try to cron job this it is not renewing the certificates and when I check the sys-log I see line after line after line of errors like this.

What is the problem and how do I fix it. I had it temporarily running every minute just so I could test it real quick but in general I want to run it once per week.

          • /usr/sbin/certbot-auto renew --quiet --no-self-upgrade

When I run the dry-run I get this:

./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.)

I am running the cron and the dry-run as root…

I don’t get it.

Apparently this isn’t about let’s encrypt it is some problem with linux and you need to change the root password.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.