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
Our implementation of the HTTP-01 challenge follows redirects, up to 10 redirects deep. It only accepts redirects to “http:” or “https:”, and only to ports 80 or 443. It does not accept redirects to IP addresses. When redirected to an HTTPS URL, it does not validate certificates (since this challenge is intended to bootstrap valid certificates, it may encounter self-signed or expired certificates along the way).
I think acme_tiny should behave the same.
i did the following modification localy and post it here in case you want to re-use it ! acme.diff.txt
The text was updated successfully, but these errors were encountered:
Your patch is very similar to #230; see #221 for a better implementation which only disables certificate verification in this one case. If you want to use something like this, please use the patch from #221!
I ran into this bug while generation certificate for third party software that manage itself apache configuration and force redirection to https.
In this context, the first certificate generation fail because https cert is auto-signed.
letsencrypt politic about self-signed certs (https://letsencrypt.org/fr/docs/challenge-types/) :
I think acme_tiny should behave the same.
i did the following modification localy and post it here in case you want to re-use it !
acme.diff.txt
The text was updated successfully, but these errors were encountered: