Manual Method: Invalid key authorization: 1 parts



I ran the command for the manual method:
./letsencrypt-auto certonly -a manual -d --server --agree-dev-preview

I created the requested file 4fRex1xoxIxymyxGyyxsxYVxzo2Q3soQd_GbEHodLxkiIUCxU_dc_7w that contains the text 4fRex1xoxIxymyxGyyxsxYVxzo2Q3soQd_GbEHodLxkiIUCxU_dc_7w


curl -v

* About to connect() to port 80 (#0)
*   Trying connected
> GET /.well-known/acme-challenge/4fRex1xoxIxymyxGyyxsxYVxzo2Q3soQd_GbEHodLxkiIUCxU_dc_7w HTTP/1.1
> User-Agent: curl/7.23.1 (x86_64-pc-win32) libcurl/7.23.1
> Host:
> Accept: */*
< HTTP/1.1 200 OK
< Server: Cowboy
< Connection: keep-alive
< X-Powered-By: Express
< Access-Control-Expose-Headers: Location
< Accept-Ranges: bytes
< Cache-Control: public, max-age=0
< Last-Modified: Wed, 02 Dec 2015 19:02:03 GMT
< Etag: W/"2b-1516412a7f8"
< Content-Type: application/octet-stream
< Content-Length: 43
< Date: Wed, 02 Dec 2015 19:13:17 GMT
< Via: 1.1 vegur

And this is what I get from the client:

Failed authorization procedure. (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Error parsing key authorization file: Invalid key authorization: 1 parts

 - The following 'urn:acme:error:unauthorized' errors were reported by
   the server:

   Error: The client lacks sufficient authorization


Hello @sydney,

I don’t know if was a typo but the name of the challenge file and the content should not be the same, the content of the challenge file is a bit longer.

By the way, I can’t see the content of the file on the curl output, did you cut it when posted?. Another thing to check, the Content-Type provided by your cowboy server is application/octet-stream but should be text/plain. Review that you are creating the challenge file in the right way and second, be sure that your server uses text/plain Content-Type to server the challenge file.