Support setting CA in per-certificate config (DOMAINS_D or certs/…) #449

New Issue

adam · 2025-12-29T01:25:29+01:00

adam commented

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

Originally created by @alexs77 on GitHub (Dec 12, 2019).

It would be very good, if it were possible to set the CA on a per-certificate level.

Example: for production domains, I'd like to use the "real" Let's Encrypt CA https://acme-v02.api.letsencrypt.org/directory
For test domains, I'd like to use the staging environment https://acme-staging-v02.api.letsencrypt.org/directory

According to https://github.com/lukas2511/dehydrated/blob/master/docs/per-certificate-config.md, the confguration variable CA cannot be changed in certs/example.org/config or DOMAINS_D/example.org.

Originally created by @alexs77 on GitHub (Dec 12, 2019). It would be very good, if it were possible to set the CA on a per-certificate level. Example: for production domains, I'd like to use the "real" Let's Encrypt CA https://acme-v02.api.letsencrypt.org/directory For test domains, I'd like to use the staging environment https://acme-staging-v02.api.letsencrypt.org/directory According to https://github.com/lukas2511/dehydrated/blob/master/docs/per-certificate-config.md, the confguration variable `CA` cannot be changed in `certs/example.org/config` or `DOMAINS_D/example.org`.

adam closed this issue

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

adam commented

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

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

This is not possible in the way dehydrated is currently structured. Closing this as it would require a major rewrite.

@lukas2511 commented on GitHub (Dec 10, 2020): This is not possible in the way dehydrated is currently structured. Closing this as it would require a major rewrite.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#449