CERTBOT automatic renewal: Will "1 certificate per domain" be maintained?

I like this automated solution, but need to maintain “one certificate per domain” even after the auto renewal occurs.

I have automated the CERTBOT client with crontab -e

#
# LetsEncrypt Daily Auto Renewal Check with certbot ACME client
#
21 8 * * * /usr/bin/letsencrypt renew

When the cronjob runs I get an email that the cronjob has run successfully.

-----Original Message-----
From: Cron Daemon [mailto:root@myserver.com]
Sent: Tuesday, December 13, 2016 12:41 PM
To: root@myserver.com
Subject: Cron root@northpawfamilycloud /usr/bin/letsencrypt renew

Processing
/etc/letsencrypt/renewal/calendar.northpawfamilycloud.xyz.conf

The following
certs are not due for renewal yet:

/etc/letsencrypt/live/calendar.northpawfamilycloud.xyz/fullchain.pem
(skipped) No renewals were attempted.

-----END Original Message-----

I plan to install several other LetsEncrypt certificates individually, as opposed to many domains all on one certificate.

My question is when the certificate is eligible for autorenewal will the cronjob:

21 8 * * * /usr/bin/letsencrypt renew

renew each certificate eligible for renewal individually, or will multiple domains be conglomerated into one renewal certificate composed of all the domains that were eligible for renewal when the cronjob ran ?

I like this automated solution, but need to maintain “one certificate per domain” even after the auto renewal occurs.

Ubuntu 16.04 LTS / Apache

certbot renew doesn’t change things. It reissues certificates as they originally were (following the generated configuration files in /etc/letsencrypt/renewal/). It won’t combine things.

2 Likes

Thanks

Merry Christmas !

1 Like

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