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
# If we did not get any email at all, use the default (empty mail) config
261
262
config_home="/etc/acme.sh/default"
262
-
fi
263
+
fi
263
264
264
265
local -n acme_ca_uri="ACME_${cid}_CA_URI"
265
266
if [[ -z"$acme_ca_uri" ]];then
@@ -368,13 +369,13 @@ function update_cert {
368
369
fi
369
370
else
370
371
# We don't have a Zero SSL ACME account, EAB credentials, a ZeroSSL API key or an account email :
371
-
# skip certificate account registration and certificate issuance.
372
+
# skip certificate account registration and certificate issuance.
372
373
echo"Error: usage of ZeroSSL require an email bound account. No EAB credentials, ZeroSSL API key or email were provided for this certificate, creation aborted."
Copy file name to clipboardExpand all lines: docs/Container-configuration.md
+3
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,9 @@ You can also create test certificates per container (see [Test certificates](./L
34
34
35
35
*`ACME_POST_HOOK` - The provided command will be run after every certificate issuance. The action is limited to the commands available inside the **acme-companion** container. For example `--env "ACME_POST_HOOK=echo 'end'"`. For more information see [Pre- and Post-Hook](./Hooks.md)
36
36
37
+
*`DEFAULT_RENEW` - 60 days by default, this defines the number of days between certificate renewals attempts. For certificates issued by certain Certificate Authorities, such as Buypass, which have a lifespan of 180 days, it may be advisable to initiate the renewal process on day 170 rather than the default day 60. See [BuyPass.com CA](https://github.com/acmesh-official/acme.sh/wiki/BuyPass.com-CA) for more detail.
38
+
37
39
*`ACME_HTTP_CHALLENGE_LOCATION` - Previously **acme-companion** automatically added the ACME HTTP challenge location to the nginx configuration through files generated in `/etc/nginx/vhost.d`. Recent versions of **nginx-proxy** (>= `1.6`) already include the required location configuration, which remove the need for **acme-companion** to attempt to dynamically add them. If you're running and older version of **nginx-proxy** (or **docker-gen** with an older version of the `nginx.tmpl` file), you can re-enable this behaviour by setting `ACME_HTTP_CHALLENGE_LOCATION` to `true`.
38
40
39
41
*`RELOAD_NGINX_ONLY_ONCE` - The companion reload nginx configuration after every new or renewed certificate. Previously this was done only once per service loop, at the end of the loop (this was causing delayed availability of HTTPS enabled application when multiple new certificates where requested at once, see [issue #1147](https://github.com/nginx-proxy/acme-companion/issues/1147)). You can restore the previous behaviour if needed by setting the environment variable `RELOAD_NGINX_ONLY_ONCE` to `true`.
0 commit comments