I have been troubleshooting an issue where bcd-proxy will not fetch a certificate for my domain. After reviewing the debug logs for bcd-proxy I realized the issue was that bcd-proxy didn't support ACMEv2. This is an issue as ACMEv1 is being sunset by Let's Encrypt in favor of ACMEv2 (RFC 8555)
"2020/01/04 21:10:42 http: TLS handshake error from [REDACTED]:62383: 403 urn:acme:error:unauthorized: Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details."
I have created a patch to resolve this. I'll be submitting the pull request shortly.
I have been troubleshooting an issue where bcd-proxy will not fetch a certificate for my domain. After reviewing the debug logs for bcd-proxy I realized the issue was that bcd-proxy didn't support ACMEv2. This is an issue as ACMEv1 is being sunset by Let's Encrypt in favor of ACMEv2 (RFC 8555)
"2020/01/04 21:10:42 http: TLS handshake error from [REDACTED]:62383: 403 urn:acme:error:unauthorized: Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details."
I have created a patch to resolve this. I'll be submitting the pull request shortly.