On 27 August 2017 02:30:51 GMT+02:00, "Canek Peláez Valdés"
wrote:
>On Sat, Aug 26, 2017 at 1:40 AM, Ian Zimmerman
>wrote:
>>
>> I don't understand the letsencrypt certbot renewal process,
>specifically
>> the hooks.
>>
>> I have two certificates: one
On Sat, Aug 26, 2017 at 1:40 AM, Ian Zimmerman wrote:
>
> I don't understand the letsencrypt certbot renewal process, specifically
> the hooks.
>
> I have two certificates: one for webserver, one for mailserver. I got
> them only very recently so I until now the renewal
On 26.08.2017 08:40, Ian Zimmerman wrote:
> The cop-out solution is to have a single pre-hook and a single
> post-hook, which stop (resp. start) both daemons, but that is
> ugly. How do people handle this?
I have not used certbot hooks myself, but a glance at the docs shows:
--pre-hook and
I don't understand the letsencrypt certbot renewal process, specifically
the hooks.
I have two certificates: one for webserver, one for mailserver. I got
them only very recently so I until now the renewal cronjob has always
been a no-op, but the real thing will happen very soon. When it does,
4 matches
Mail list logo