Originally created by @lukas2511 on GitHub (Mar 11, 2018).
Currently if dehydrated fails to generate a chain it will repeat the whole process of acquiring a certificate on the next run.
Ideally it should use the previously acquired certificate and only fix the chain certificate and symlinks on the next run.
Originally created by @lukas2511 on GitHub (Mar 11, 2018).
Currently if dehydrated fails to generate a chain it will repeat the whole process of acquiring a certificate on the next run.
Ideally it should use the previously acquired certificate and only fix the chain certificate and symlinks on the next run.
This is no longer relevant as ACMEv2 delivers the whole chain and the underlying issue should never occur that way.
@lukas2511 commented on GitHub (Apr 8, 2018):
This is no longer relevant as ACMEv2 delivers the whole chain and the underlying issue should never occur that way.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @lukas2511 on GitHub (Mar 11, 2018).
Currently if dehydrated fails to generate a chain it will repeat the whole process of acquiring a certificate on the next run.
Ideally it should use the previously acquired certificate and only fix the chain certificate and symlinks on the next run.
@lukas2511 commented on GitHub (Apr 8, 2018):
This is no longer relevant as ACMEv2 delivers the whole chain and the underlying issue should never occur that way.