Option to continue fetching certificate if some alternative names don't work #507

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

Originally created by @thegushi on GitHub (Nov 25, 2020).

Hey there

It would be useful to have an option to continue fetching a certificate if not all alternative names work. Sometimes multiple domains point to a single vhost, and if one of them expires it would be good to still get a cert for the remaining, valid, names.

For this purpose, I would typically use a challenge which will always pass as the "main" domain name.

From the looks of the way dehydrated works, this would probably require restarting the issuance process for a given cert, only for alternatives which have passed the challenges.

My specific use case is that when I give a person a domain name to use, I want to be able to fire up lets-encrypt with something, even if their domain name is not pointing at my server yet, so I create a private name (like theirtempsite.myhostingco.com).

Originally created by @thegushi on GitHub (Nov 25, 2020). Hey there It would be useful to have an option to continue fetching a certificate if not all alternative names work. Sometimes multiple domains point to a single vhost, and if one of them expires it would be good to still get a cert for the remaining, valid, names. For this purpose, I would typically use a challenge which will always pass as the "main" domain name. From the looks of the way dehydrated works, this would probably require restarting the issuance process for a given cert, only for alternatives which have passed the challenges. My specific use case is that when I give a person a domain name to use, I want to be able to fire up lets-encrypt with *something*, even if their domain name is not pointing at my server yet, so I create a private name (like theirtempsite.myhostingco.com).
adam closed this issue 2025-12-29 01:26:27 +01:00
Author
Owner

@lukas2511 commented on GitHub (Dec 10, 2020):

This will not really work. The signing request is generated before any validation starts. If any domain is not validated the certificate order will fail completely.

@lukas2511 commented on GitHub (Dec 10, 2020): This will not really work. The signing request is generated before any validation starts. If any domain is not validated the certificate order will fail completely.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#507