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: devb2be.bondwith.me
I ran this command:
./certbot-auto certonly -w /usr/share/nginx/html/testb2be.bondwith.me -d testb2be.bondwith.me
It produced this output:
./certbot-auto certonly -w /usr/share/nginx/html/testb2be.bondwith.me -d testb2be.bondwith.me
Saving debug log to /var/log/letsencrypt/letsencrypt.log
How would you like to authenticate with the ACME CA?
1: Apache Web Server plugin - Beta (apache)
2: Nginx Web Server plugin (nginx)
3: Spin up a temporary webserver (standalone)
4: Place files in webroot directory (webroot)
Select the appropriate number [1-4] then [enter] (press ‘c’ to cancel): 4
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for testb2be.bondwith.me
Using the webroot path /usr/share/nginx/html/testb2be.bondwith.me for all unmatched domains.
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. testb2be.bondwith.me (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://testb2be.bondwith.me/.well-known/acme-challenge/2jFgpYPpoCOuaH01WcdDC7g7Bi4dcSggD5Rit61PhK8: “\n\n404 Not Found\n\n
Not Found
\n<p”IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: testb2be.bondwith.me
Type: unauthorized
Detail: Invalid response from
http://testb2be.bondwith.me/.well-known/acme-challenge/2jFgpYPpoCOuaH01WcdDC7g7Bi4dcSggD5Rit61PhK8:
“\n\n404 Not
Found\n\nNot Found
\n<p”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.
My web server is (include version):
Apache (httpd) is using port 80 for http and port 443 for https. The nginx is also just newly setup and it is using port 8080 for http and port 8443 for https. The existing hostname “devb2be.bondwith.me” has already been setup previously with let’s encrypt.
The operating system my web server runs on is (include version):
OS version = Centos Linux release 7.5.1804(Core)
Apache = 2.4.6 (centos)
Nginx = 1.12.2
My hosting provider, if applicable, is: N/A
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): Not using any cpanel.
Other misc highlights
-
I am using the old method of git clone letsencrypt to get this letsencrypt to work.
-
This new centos 7 has package comes with certbot, I’m not sure if i have to install this centos package certbot to make this work for the issues or perhaps no? Need your advise.