Domains: sambidb.com, kizunadb.com, l4jp.com (the first two are wildcard certs)
I’m on a Linode VPS, with CentOS 7.4 and nginx 1.10.2, with my first experience using Let’s Encrypt. It’s now a couple days into the period when the auto-renew should have done something - the expiry is Jan. 31st. I’m still a complete newbie, so I don’t know how to troubleshoot what’s going on. Are there logs or something? I’ve looked but don’t see anything relevant.
When I first set it up, it was somewhat stubborn to get the TXT record for the verification because Linode is very slow to propagate (15-16 minutes, and even then, it doesn’t work every time), but it worked on about the third or fourth try for each domain. See this thread for the info about my setup, and note my last comment on that thread where I realize that I should already have what’s needed for renewal: No TXT record found (using Linode DNS plugin)
When I installed stuff, something (the Linode plugin?) created the following files for renewals:
/lib/systemd/system/certbot-renew.service
[Unit]
Description=This service automatically renews any certbot certificates found
[Service]
EnvironmentFile=/etc/sysconfig/certbot
Type=oneshot
ExecStart=/usr/bin/certbot renew $PRE_HOOK $POST_HOOK $RENEW_HOOK $CERTBOT_ARGS
/lib/systemd/system/certbot-renew.timer
[Unit]
Description=This is the timer to set the schedule for automated renewals
[Timer]
OnCalendar=daily
RandomizedDelaySec=6hours
Persistent=true
[Install]
WantedBy=timers.target
Running certbot certificates, I get this:
Found the following certs:
Certificate Name: kizunadb.com
Domains: kizunadb.com *.kizunadb.com
Expiry Date: 2019-01-31 07:55:06+00:00 (VALID: 28 days)
Certificate Path: /etc/letsencrypt/live/kizunadb.com/fullchain.pem
Private Key Path: /etc/letsencrypt/live/kizunadb.com/privkey.pem
Certificate Name: l4jp.com
Domains: l4jp.com
Expiry Date: 2019-01-31 08:43:44+00:00 (VALID: 28 days)
Certificate Path: /etc/letsencrypt/live/l4jp.com/fullchain.pem
Private Key Path: /etc/letsencrypt/live/l4jp.com/privkey.pem
Certificate Name: sambidb.com
Domains: *.sambidb.com
Expiry Date: 2019-01-31 06:31:47+00:00 (VALID: 28 days)
Certificate Path: /etc/letsencrypt/live/sambidb.com/fullchain.pem
Private Key Path: /etc/letsencrypt/live/sambidb.com/privkey.pem
I don’t know how to determine if the renew service has been firing daily like it’s supposed to, and if so, what happened the last two days when it should have actually attempted a renewal. Can you point me to the right tools to diagnose the situation? (I have not attempted a manual renewal, because if it succeeded, I would have to wait another 60 days before I could work on this. If the time gets close I’ll do a manual one, but first I want to try getting auto working.)
and yes on the time left.
I'm hoping for an alert when the expiry is getting close, not past.