acme.sh no longer using Let's Encrypt

[greenshrike]

Looks like acme is now defaulting to using ZeroSSL for certs:

configuring Let's Encrypt

[Thu Oct 7 15:43:27 EDT 2021] Using CA: https://acme.zerossl.com/v2/DV90 [Thu Oct 7 15:43:27 EDT 2021] Create account key ok. [Thu Oct 7 15:43:28 EDT 2021] No EAB credentials found for ZeroSSL, let's get one [Thu Oct 7 15:43:28 EDT 2021] acme.sh is using ZeroSSL as default CA now. [Thu Oct 7 15:43:28 EDT 2021] Please update your account with an email address first. [Thu Oct 7 15:43:28 EDT 2021] acme.sh --register-account -m my@example.com [Thu Oct 7 15:43:28 EDT 2021] See: https://github.com/acmesh-official/acme.sh/wiki/ZeroSSL.com-CA [Thu Oct 7 15:43:28 EDT 2021] Please add '--debug' or '--log' to check more details. [Thu Oct 7 15:43:28 EDT 2021] See: https://github.com/acmesh-official/acme.sh/wiki/How-to-debug-acme.sh

TLS Certificate Issue failed

From https://github.com/acmesh-official/acme.sh/wiki/Server, it looks like adding '--server letsencrypt' to the request command (worked for me) or running 'acme.sh --set-default-ca --server letsencrypt' previous to requesting a cert (untested) will make acme revert to Let's Encrypt.

-- letsencrypt.sh.orig 2021-10-07 15:58:05.604493000 -0400
+++ letsencrypt.sh      2021-10-07 15:55:43.794442000 -0400
@@ -401,3 +401,3 @@
        local _acme="/root/.acme.sh/acme.sh"
-       if $_acme --issue --force -d "$TOASTER_HOSTNAME" -w "$_HTTPDIR"; then
+       if $_acme --server letsencrypt --issue --force -d "$TOASTER_HOSTNAME" -w "$_HTTPDIR"; then
                update_haproxy_ssld