Is it possible to use CONTACT_EMAIL only for certain vhosts on a server? #477

New Issue

2025-12-29T01:25:56+01:00

adam commented

2025-12-29 01:25:56 +01:00

Originally created by @dave559 on GitHub (May 4, 2020).

Is it possible to use CONTACT_EMAIL only for certain vhosts on the same server?

We have started to use the CONTACT_EMAIL config setting, because, very occasionally, certs fail to renew (usually a problem somewhere at our end, I hasten to add), and this will email us a reminder if a cert doesn't renew timeously.

As part of our website setup processes, we often serve a staging site under a temporary hostname before updating the hostname. Unfortunately, this means that LetsEncrypt now (understandably) emails us when the certs for these transient hostnames are due to expire.

Is there a way in dehydrated to only use the CONTACT_EMAIL setting for specific hostnames, and not for others?

Originally created by @dave559 on GitHub (May 4, 2020). Is it possible to use CONTACT_EMAIL only for certain vhosts on the same server? We have started to use the CONTACT_EMAIL config setting, because, very occasionally, certs fail to renew (usually a problem somewhere at our end, I hasten to add), and this will email us a reminder if a cert doesn't renew timeously. As part of our website setup processes, we often serve a staging site under a temporary hostname before updating the hostname. Unfortunately, this means that LetsEncrypt now (understandably) emails us when the certs for these transient hostnames are due to expire. Is there a way in dehydrated to only use the CONTACT_EMAIL setting for specific hostnames, and not for others?

adam closed this issue

2025-12-29 01:25:56 +01:00

adam commented

2025-12-29 01:25:57 +01:00

@lukas2511 commented on GitHub (May 4, 2020):

Since the contact email is for the account and not for the individual certificates there isn't any way to easily configure this. You could in theory hold multiple dehydrated instances, one with contacts one without, but the far far better solution would probably to set up your own certificate monitoring instead of relying on LE to send the notifications.

@lukas2511 commented on GitHub (May 4, 2020): Since the contact email is for the account and not for the individual certificates there isn't any way to easily configure this. You could in theory hold multiple dehydrated instances, one with contacts one without, but the far far better solution would probably to set up your own certificate monitoring instead of relying on LE to send the notifications.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#477