Acme.sh is updating their defaults to use zerossl instead of letsencrypt [0]. This has resulted in errors like: Can not resolve _eab_id When our runs of acme.sh attempt to communicate with zerossl. While the default change isn't supposed to happen until August 1 we hit it early because we consume the dev branch of acme.sh. We avoid this entirely by being explicit about the server to communicate to in our acme.sh driver script. We explicitly set --server to letsencrypt. 3d5d2779d2?style=unified&whitespace=

master
Julian Qian 2023-06-29 11:10:17 +08:00
parent 989d1aafa4
commit 8e24417dd1
1 changed files with 1 additions and 1 deletions

@ -47,7 +47,7 @@ Now it's time to create the certificate for your domain:
$ cd /usr/local/share/acme.sh
$ export CERT_DOMAIN="your-domain.tld"
$ export CERT_DNS="dns_cf"
$ ./acme.sh --issue --home . -d "$CERT_DOMAIN" --dns "$CERT_DNS"
$ ./acme.sh --issue --server letsencrypt --home . -d "$CERT_DOMAIN" --dns "$CERT_DNS"
```
## Deploy the default certificate