From 8e24417dd1307360a2bb710d6b295a5a2348b69d Mon Sep 17 00:00:00 2001 From: Julian Qian Date: Thu, 29 Jun 2023 11:10:17 +0800 Subject: [PATCH] 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. https://opendev.org/opendev/system-config/commit/3d5d2779d284af52c23af69ae4fc1a99e7ecdcbc?style=unified&whitespace= --- Synology-NAS-Guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Synology-NAS-Guide.md b/Synology-NAS-Guide.md index b723b9f..e23a568 100644 --- a/Synology-NAS-Guide.md +++ b/Synology-NAS-Guide.md @@ -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