UTF8 problem about acme-tiny HOT 3 CLOSED

this sounds like the challange token as delivered by your webserver is somehow in a non-utf8 format.
Can you check what this file looks like?

from acme-tiny.

I had the same issue with nginx: It was just sending a few bytes of garbage (according to fiddler). No headers, nothing.
As soon as I disabled http2 on all of my non ssl redirect/acme sites, the acme-challenges where served correctly. Turns out http2 must only be used together with the ssl parameter:

https://www.nginx.com/blog/nginx-plus-r7-released/

Please note HTTP/2 is only supported when the ssl parameter is also included

nginx version: nginx/1.9.10
built with OpenSSL 1.0.2e 3 Dec 2015 (running with OpenSSL 1.0.2f 28 Jan 2016)

Certainly not an acme-tiny issue 👍

from acme-tiny.

Thanks @nappy closing issue after http2 clarification.

from acme-tiny.