Magnus Andriy Mahats Is it possible to implement HTTP-01 challenge of Buypass to follow HTTP to HTTPS redirect to validate at least on the same domain (e.g. Redirect http://example.com to https://example.com to complete validation should be valid) ?
Today most SLL enable website HTTPS redirection on their own domain.
RFC8555 also permit to follow redirect: https://tools.ietf.org/html/rfc8555#section-8.3
Let's Encrypt implements this follow redirect mechanism since 2018 or before: https://community.letsencrypt.org/t/i-must-turn-off-https-redirect-to-renew/70415/4
Thanks for the new release to support 5 FQDNs now.
I do notice that domains in puny code is not supported.
I was getting below response when I was trying to get a certificate in puny code.
[type] => urn:ietf:params:acme:error:rejectedIdentifier
[detail] => Domain is rejected as high-risk [code] => 403
[message] => REJECTED_IDENTIFIER
[details] => HTTP 403 Forbidden
May I ask if you have any plan to allow certificates in puny code? I know there aren't too many people using utf-8 domains, it will still be nice for you to support it.