You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[HTTP Server] http: TLS handshake error from 127.0.0.1:35816: 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.
To Reproduce
Steps to reproduce the behavior: app.Run(iris.AutoTLS(":443", "example.com", "[email protected]"))
The text was updated successfully, but these errors were encountered:
Hello @stefanwuthrich, they change something(letsencrypt) because it was working a time ago. Will take look at this later on. In the meantime, as you probably already know , you can use caddy in front of Iris which gives you more control on production usage with multiple Iris web applications and endpoints.
Thanks for the bug report, if you can find the origin of the issue it would be very helpful for me as I am preparing for the v12.1.0 release.
OK @stefanwuthrich the issue is fixed when you update the golang.org/x/crypto package , which implements the RFC 8555 by-default. The iris v12.1.0 will contain an updated go.mod file which will include this package latest version too;
Describe the bug
When I try to use AutoTLS I get:
[HTTP Server] http: TLS handshake error from 127.0.0.1:35816: 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.
To Reproduce
Steps to reproduce the behavior:
app.Run(iris.AutoTLS(":443", "example.com", "[email protected]"))
The text was updated successfully, but these errors were encountered: