Hi,
> Mhh, are you sure? The default with HOOK_CHAIN=no is:
> request_challenge → deploy_challenge → testing_challenge →
> clean_challenge
> repeated for each domain in domains.txt…, and that is still true with
> the latest 0.6.5.
Looking at the code of the installed backports package,
On Sun, Oct 20, 2019 at 01:31:26AM +0200, Florian Zumbiehl wrote:
> unfortunately, that version (0.6.2-2+deb10u1~bpo9+1) is not backwards
> compatible with the current stretch version (0.3.1-3+deb9u2), in that it
> deploys all challenges for a certificate at once, and only then submits the
>
Hi,
> In fact, the proposed "fix" I'm working on is to actually get the
> version that is currently in backports directly in the oldstable
> distribution, but I need to tweak it a bit as to do that I need to
> reintroduce the 'letsencrypt.sh' compatibility packages/scripts.
unfortunately, that
On Sat, Oct 19, 2019 at 08:14:33PM +0200, Florian Zumbiehl wrote:
> Is there any plan to fix this bug before then, or will users have to work
> around this individually to avoid running into expired certificates? And if
> the latter, what is the recommended workaround? Is the current backports
>
Hi,
as the recommended strategy by LetsEncrypt is to renew certificates 30 days
before their expiry, and we are approaching 30 days since the change that
exposed this bug that thus is preventing certificate renewal since then,
certificates generated using dehydrated are going to start expiring in
5 matches
Mail list logo
