Nicholas Morsman

Hi @jsha and thanks for reporting this, CSR signing using SHA-256 should be fixed in 64b7340b82b70dd4108fef3c854806ad8d5de712 and has been published with `[email protected]`. The fix has also been backported to `[email protected]`...

Added an [upgrade notice](https://github.com/publishlab/node-acme-client#important-upgrade-notice) with some details to the `README` and `CHANGELOG` in case this goes by unnoticed.

@FLYBYME Your issue looks like https://github.com/publishlab/node-acme-client/issues/63, either upgrade to Node >= v16 or stick to acme-client v4.

Hi, unable to reproduce this. What exactly are your `commonName` and `altNames` that are causing the error? ```javascript (async () => { const [key, csr] = await acme.crypto.createCsr({ commonName: '*.example.org',...

The value you've stored in `let privateKey = ...` is your **account key**, used to identify you with Let's Encrypt. What you want to use along with the certificate for...

Thanks for raising this, bug in `auto()` with no common name fixed in 9e277b5aedc380644f8de8982b60c6407f3406af, docs and examples in 12f8096f2cf7ca377d63dbfffad0a90ed605379c.

Yep you are right @bchr02 - nuking all TXT records within `_acme-challenge.domain.tld` from `challengeRemoveFn()` will likely sabotage wildcard certificate issuance since it requires two TXT records, and the other challenge...