I think you gave us the wrong link because that’s not a DO guide.
I’m a little confused by why there is no output in that log file other than the OS package update information, but I’ll point out that you aren’t using
renew as we intended it to be used. The default behavior of
certbot renew is to check each installed certificate’s expiration date and renew it if it’s less than 30 days away from expiry.
Because of that,
certbot renew can be run very frequently—we recommend running it twice per day. It will almost always look at the local certificates and decide that no action is necessary yet.
Although I don’t know why you don’t see messages to this effect in your logs, I’m guessing that the
renew script decided that no action was necessary and therefore didn’t take any action.
There is a form
--force-renewal where every certificate is forced to be renewed immediately, regardless of how close to expiry it is, but for various reasons we don’t recommend using that from
cron. If you do want the certificate to be renewed sooner than 30 days before expiry, you can edit the renewal configuration files in
/etc/letsencrypt/renewal and set
renew_before_expiry to a higher value than the default
30 days (bearing in mind that if you choose a value higher than 82 days or if you have multiple certificates for subdomains of the same domain, you might run into rate limits from the certificate authority side).
For comparison, you could check what happens when you simply run
/opt/letsencrypt/letsencrypt-auto renew yourself on the command line. Hopefully it will say something to the effect that it checked your local certificates and found that none of them were due for renewal yet.
Also, depending on what plugin you used, you may not need to reload nginx explicitly from your cron job. (With
--nginx you probably don’t, while with
--webroot you probably do.) Rather than always reloading nginx after running the renewal script, we have a form called
--deploy-hook where you can say
--deploy-hook "service nginx reload" or similar, in which case Certbot itself will run this command after obtaining new certificates.