Fix chain if certificate has already been acquired #297

Closed
opened 2025-12-29 01:21:25 +01:00 by adam · 1 comment
Owner

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.
adam closed this issue 2025-12-29 01:21:25 +01:00
Author
Owner

@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.

@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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#297