Did caddy create /etc/cron.d/certbot?

Hey all,

I used to manually generate my certificates on my nginx using letsencrypt, now I’m on caddy and everything is simple :slight_smile:

My problem is, I have a cron job that fails to renew certificate but I don’t know if it’s a remnant of my previous nginx/letsencrypt install (and I should do some cleaning) or if it’s caddy’s business (and I should worry).

The file is /etc/cron.d/certbot

# /etc/cron.d/certbot: crontab entries for the certbot package
#
# Upstream recommends attempting renewal twice a day
#
# Eventually, this will be an opportunity to validate certificates
# haven't been revoked, etc.  Renewal will only occur if expiration
# is within 30 days.
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

0 */12 * * * root test -x /usr/bin/certbot && perl -e 'sleep int(rand(3600))' && certbot -q renew

This cron job attempts to renew certificates located in /etc/letsencrypt/live.

Does all this have anything to do with Caddy?

Thanks for your help!

Nope, that has nothing to do with Caddy.

2 Likes

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