Letsencrypt commands are pointed to ZeroSSL by default

commands referencing lets encrypt, e.g. wo site update example.com -le, are sending requests to ZeroSSL by default instead of LetsEncrypt.

The problem is caused by line 32 in /etc/letsencrypt/acme.sh, where the default CA is set to ZeroSSL instead of LetsEncrypt.

[renatofrota]

@nova0052 You may need to --letsencrypt inside the WordOps codebase where its calling acme.sh

Sorry, I don’t understand your meaning.

I’m already using the --letsencrypt parameter, the problem is that the parameter is ignored and acme.sh is using ZeroSSL instead of LetsEncrypt.

WordOps developers could not predict acme.sh would someday change it’s default CA from Let’s Encrypt to ZeroSSL. Money talks, apilayer (Idera, Inc) acquired ZeroSSL and also acquired (or just partnered?) acme.sh developers and ZeroSSL is now the default CA of acme.sh script.

The WordOps parameter “–letsencrypt” should have been named “–acmesh” or something like that. Maybe it’s too late to change. Probably WordOps will set acme.sh default CA to letsencrypt, what is very easy (acme.sh --set-default-ca --server letsencrypt) and works flawlessly. Those who have problems with LE certificate issuance rate limit (which is not a problem for me) may change the default to ZeroSSL manually.

[tersor]

Acme.sh v3.0.0 is using ZeroSSL as default CA. If you run into any issues in WordOps creating new certs, you have two options:

1. Roll with Acme and register a ZeroSSL account:

acme.sh --register-account -m [e-mail]

1. Tell Acme to use Letsencrypt as default CA:

acme.sh --set-default-ca --server letsencrypt