Select the appropriate number [1-2] then [enter] (press ‘c’ to cancel): 2
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://example.com/.well-known/acme-challenge/zh6KGGNQ43IkdCyrlv3Y3ucauVdt4-EDVfpMGPU8y30: "\n<html xmlns=“http:”
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
curl -X GET -I http://example.com/.well-known/acme-challenge/test.txt
HTTP/1.1 404 Not Found
Server: nginx/1.14.1
Date: Mon, 28 Jan 2019 07:39:37 GMT
Content-Type: text/html
Content-Length: 11812
Connection: keep-alive
Last-Modified: Mon, 18 Nov 2013 21:26:36 GMT
Accept-Ranges: bytes
if you have trouble to use http-01 - validation, a lot of domain + command - specific errors are possible.
So please answer the following questions of the #help - category:
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know):
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
I ran the following command
sudo certbot certonly -d klock-in.com -d www.klock-in.com
[sudo] password for reza:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
How would you like to authenticate with the ACME CA?
1: Nginx Web Server plugin - Alpha (nginx)
2: Spin up a temporary webserver (standalone)
3: Place files in webroot directory (webroot)
Select the appropriate number [1-3] then [enter] (press ‘c’ to cancel): 3
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for www.klock-in.com
http-01 challenge for klock-in.com
Input the webroot for www.klock-in.com: (Enter ‘c’ to cancel): /itconquest/smallsites/sites-src/klock-in.com/app-landing
curl -X GET -I http://klock-in.com/.well-known/acme-challenge/test
HTTP/1.1 404 Not Found
Server: nginx/1.14.1
Date: Mon, 28 Jan 2019 09:52:28 GMT
Content-Type: text/html
Content-Length: 11812
Connection: keep-alive
Last-Modified: Mon, 18 Nov 2013 21:26:36 GMT
Accept-Ranges: bytes
Using nginx as a reverse proxy
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
Your non www sends http, your www is redirected to https. The wrong certificate isn't a problem, Letsencrypt ignores that.
But is your webroot really correct with this setting?
Perhaps remove the redirect http -> https of your www version (directory /.well-known), so both requests (www + non-www) are answered from the same server.
Changed and this is my rest configs. It’s my docker-container configs. All other websites are working fine with the same configs, but this one isn’t working.
How would you like to authenticate with the ACME CA?
1: Nginx Web Server plugin - Alpha (nginx)
2: Spin up a temporary webserver (standalone)
3: Place files in webroot directory (webroot)
Select the appropriate number [1-3] then [enter] (press ‘c’ to cancel): 3
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for www.klock-in.com
http-01 challenge for klock-in.com
Input the webroot for www.klock-in.com: (Enter ‘c’ to cancel): /itconquest/smallsites/sites-src/klock-in.com/app-landing
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.