Date: Mon, 9 Sep 2019 12:12:55 +0200 (CEST) From: =?UTF-8?Q?Trond_Endrest=C3=B8l?= <trond.endrestol@ximalas.info> To: Victor Sudakov <vas@mpeks.tomsk.su> Cc: freebsd-security@freebsd.org Subject: Re: Let's Encrypt Message-ID: <alpine.BSF.2.21.99999.352.1909091206360.18927@enterprise.ximalas.info> In-Reply-To: <20190909090605.GA97856@admin.sibptus.ru> References: <20190908145835.GA67269@admin.sibptus.ru> <20190909090605.GA97856@admin.sibptus.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 9 Sep 2019 16:06+0700, Victor Sudakov wrote: > The majority is for py-certbot, so I'll probably use it. Thank you. I have found it prudent to run certbot twice a month from cron(8), just to be safe. Last year, I had one case where the certificate expired a few hours before the next run of certbot. Had I run certbot on the 1st and on the 15th day of each month, then the certificates would have been updated ahead of their expiration. E.g.: #minute hour mday month wday who command 52 4 1 * * root certbot renew --quiet --pre-hook "service apache24 stop" --post-hook "service apache24 start" 52 1 15 * * root certbot renew --quiet --pre-hook "service apache24 stop" --post-hook "service apache24 start" -- Trond.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.99999.352.1909091206360.18927>