By mrparker
I followed this tutorial: https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-14-04
I got to the part where the command is ./letsencrypt-auto and it returns this:
Failed authorization procedure. example.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://example.com/.well-known/acme-challenge/QPUDzybZszvcrjQ1a7ShzMHBbiq8pYCmbN1y8p_K5Dw [server_ip]: 404, www.example.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.example.com/.well-known/acme-challenge/VtyUCMvp2hX_80e-x84T-X8Be94xPiPiPsBxbj_pP04 [server_ip]: 404
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: example.com
Type: unauthorized
Detail: Invalid response from http://example.com/.well-known
/acme-challenge/QPUDzybZszvcrjQ1a7ShzMHBbiq8pYCmbN1y8p_K5Dw
[server_ip]: 404
Domain: www.example.com
Type: unauthorized
Detail: Invalid response from http://www.example.com/.well-
known/acme-challenge/VtyUCMvp2hX_80e-x84T-X8Be94xPiPiPsBxbj_pP04
[server_ip]: 404
The site redirects to https automatically using nginx config, and this error is returned whenever i run the renewal command.
The directory .well-known exists on the server, even in the browser it returns 404, which I don’t know why.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
I have the same problem here. mrparker, have you find the solution? Would you mind to share/update it here? Thanks.
Solve issue of the same exact error message and 404 as @mrparker had. What I did was:
.well-known folder for some reason, so I added an empty one with mkdir .well-knownsudo letsencrypt certonly -a webroot --webroot-path=/var/www/html -d example.com -d www.example.com and it renewed it properly and gave me the “congrats!” messagesudo service nginx reload and then sudo letsencrypt renew --force-renew and I no longer got the 404 error for the renew, then did sudo service nginx reload againHope this helps someone.
same here!! Failed authorization procedure. www.whatever.xyz (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.whatever.xyz/.well-known/acme-challenge/KHgDiTKrSrPK4a9F6t_kqZB6S-jjjyAcIZQ66SFl14I:
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.