Issuance Failed Challenge

[kelunik]

Issuance Failed Challenge

[gavinggordon]

Nevermind; Fixed the problem. It was an error on my end.

[kelunik]

@gavinggordon Could you explain the issue? Maybe I can add a better error message or others having similar issues can read it at least.

[fernandodrf]

I am having the same problem to renew my Let's Encrypt certificates:

$ php acme-client/bin/acme issue -s letsencrypt -d URL.com:www.URL.com -p $HOME/public_html:$HOME/public_html

    Providing payload at http://www.URL.com/.well-known/acme-challenge/ZGjskxbRBJcDPyrJVBpPB2DFCAZrQAzlmOVuZsQUW4k
    Providing payload at http://URL.com/.well-known/acme-challenge/mQ40x_WaUFcJeWGdxOf5sSPIzuYJ7id547CFmMmMNoQ
selfVerify failed, please check http://www.URL.com/.well-known/acme-challenge/ZGjskxbRBJcDPyrJVBpPB2DFCAZrQAzlmOVuZsQUW4k.
selfVerify failed, please check http://URL.com/.well-known/acme-challenge/mQ40x_WaUFcJeWGdxOf5sSPIzuYJ7id547CFmMmMNoQ.
Kelunik\Acme\AcmeException: Issuance failed, not all challenges could be solved. in $HOME/acme-client/src/Commands/Issue.php:104

Any ideas? The server has PHP 7.1

[kelunik]

@fernandodrf Did the client create .well-known/acme-challenge in the right place? If you place a file inside it, can you access it through your web server?

[NeilStrickland]

I had a similar problem. I also thought that the script was not actually putting anything in .well-known/acme-challenge, but after inspecting the source code, I understood that the relevant catch() clause deletes the file before re-throwing the error. While that keeps things tidy, it also makes it harder to understand what is happening. Later I understood that the firewall configuration for this development machine was preventing the letsencrypt server from fetching the challenge file. It would be useful to have a more comprehensible error message that mentions this possibility explicitly.