Closed f0rza closed 3 years ago
Are you specifying usePostAsGet
in your constructor for the AcmeProtocolClient
? Let's Encrypt servers stopped supporting unauthenticated GET's last year: https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unauthenticated-resource-gets/74380
Works perfectly with usePostAsGet
Thank you, Eugene!
On Wed, Jul 7, 2021 at 9:39 AM Eugene Bekker @.***> wrote:
Are you specifying usePostAsGet in your constructor for the AcmeProtocolClient? Let's Encrypt servers stopped supporting unauthenticated GET's last year: https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unauthenticated-resource-gets/74380
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/PKISharp/ACMESharpCore/issues/58#issuecomment-875568442, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABR5OBWSUT4Y4NH77AX2LYLTWRDHZANCNFSM475KW5MQ .
-- Best Regards, Vadym
No problem, and thanks to @WouterTinus for this enhancement a while back.
Duplicate of #42
After 2 years of work with no issues GetAuthorizationDetailsAsync started giving an error:
https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/83121408