You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this example: `web` and `app` generate a certificate using the global/default configuration. However `othersite` will perform it's certificate verification using a specific DNS-01 API configuration.
`LETSENCRYPT_uniqueidentifier_EMAIL` : must be a valid email and will be used by Let's Encrypt to warn you of impeding certificate expiration (should the automated renewal fail).
59
78
60
79
`LETSENCRYPT_uniqueidentifier_KEYSIZE` : determines the size of the requested private key. See [private key size](./Let's-Encrypt-and-ACME.md#private-key-size) for accepted values.
61
80
62
81
`LETSENCRYPT_uniqueidentifier_TEST` : if set to true, the corresponding certificate will be a test certificates: it won't have the 5 certs/week/domain limits and will be signed by an untrusted intermediate (ie it won't be trusted by browsers).
63
82
83
+
DNS-01 related variables:
84
+
85
+
`ACME_uniqueidentifier_CHALLENGE`: Defaults to HTTP-01. In order to switch to the DNS-01 ACME challenge set it to `DNS-01`
86
+
87
+
`ACMESH_uniqueidentifier_DNS_API_CONFIG`: Defaults to the values of DNS_API_CONFIG. However if you wish to specify a specific DNS-01 verification method on a particular standalone certificate. It must be defined as a bash associative array.
88
+
89
+
Example
90
+
```bash
91
+
declare -A ACMESH_alt_DNS_API_CONFIG=(
92
+
['DNS_API']='dns_cf'
93
+
['CF_Token']='<CLOUDFLARE_TOKEN>'
94
+
['CF_Account_ID']='<CLOUDFLARE_ACCOUNT_ID>'
95
+
['CF_Zone_ID']='<CLOUDFLARE_ZONE_ID>'
96
+
)
97
+
```
98
+
64
99
### Picking up changes to letsencrypt_user_data
65
100
66
101
The container does not actively watch the `/app/letsencrypt_user_data` file for changes.
0 commit comments