I think I've found a solution (for my issue at least):
# certbot --version certbot 0.17.0 # cat /etc/letsencrypt/cli.ini deploy-hook = /srv/letsencrypt-post-renew.sh # certbot renew --dry-run ... Dry run: skipping deploy hook command: /usr/sbin/service apache2 reload ... In later versions it looks like there is a standard location for these hooks - /etc/letsencrypt/renewal-hooks/deploy - but this isn't mentioned in the 0.17 docs so I think it was added in a later version. Still, more control over the cron job would be nice - especially as the official docs (and most tutorials) assume the user is going to set up their own cron job (and I haven't been able to find any documentation that says the Ubuntu package is different and will do it for you). Refs: https://github.com/certbot/certbot/blob/v0.17.0/docs/using.rst#configuration-file https://github.com/certbot/certbot/blob/v0.17.0/docs/using.rst#renewing-certificates https://certbot.eff.org/#ubuntuxenial-other http://letsencrypt.readthedocs.io/en/latest/using.html#renewing-certificates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706409 Title: should be possible to disable certbot cron job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1706409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
