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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I ran this command: certbot certonly --dry-run -d risksheet.com -w /home/ms/public_html**
It produced this output:
root@risksheet:/etc/apache2/sites-available# certbot certonly --dry-run -d risksheet.com -w /home/ms/public_html
Saving debug log to /var/log/letsencrypt/letsencrypt.log
How would you like to authenticate with the ACME CA?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Apache Web Server plugin (apache)
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): 1
Plugins selected: Authenticator apache, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for risksheet.com
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. risksheet.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://risksheet.com/.well-known/acme-challenge/Iz-qCQBbmjPJreT\
wBhhGorcK585s1k_ZgOveWxekaTI [64.251.26.132]: "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p"
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: risksheet.com
Type: unauthorized
Detail: Invalid response from
http://risksheet.com/.well-known/acme-challenge/Iz-qCQBbmjPJreTwBhhGorcK585s1k_ZgOveWxekaTI
[64.251.26.132]: "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML
2.0//EN\">\n<html><head>\n<title>404 Not
Found</title>\n</head><body>\n<h1>Not Found</h1>\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.
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
root@risksheet:/etc/apache2/sites-available#
My web server is (include version):
root@risksheet:/etc/apache2/sites-available# **apache2 -v**
Server version: Apache/2.4.29 (Ubuntu)
Server built: 2019-04-03T13:22:37
root@risksheet:/etc/apache2/sites-available#
The operating system my web server runs on is (include version):
root@risksheet:/etc/apache2/sites-available# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
root@risksheet:/etc/apache2/sites-available#
I use godaddy for dns and this domain is set up exactly the same way as another domain I have, thebrookhavengroup.com, that works with letsencrypt. I checked the ip address. Also, risksheet.com is currently serving up the right pages. Mysterious. Please help.
Visible Content: Not Found The requested URL /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de was not found on this server. Apache/2.4.29 (Ubuntu) Server at risksheet.com Port 80
Thank you, that sort of worked. I got this from the command you suggested:
root@risksheet:/etc/apache2/sites-available# certbot certonly -a webroot -d risksheet.com -w /home/ms/public_html
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for risksheet.com
Using the webroot path /home/ms/public_html for all unmatched domains.
Waiting for verification...
Cleaning up challenges
IMPORTANT NOTES:
Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/risksheet.com/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/risksheet.com/privkey.pem
Your cert will expire on 2019-08-06. To obtain a new or tweaked
version of this certificate in the future, simply run certbot
again. To non-interactively renew all of your certificates, run
"certbot renew"
If you like Certbot, please consider supporting our work by:
ServerAdmin ms@TheBrookhavenGroup.com
DocumentRoot /home/ms/public_html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
<Directory /home/ms/public_html>
AllowOverride All
Require all granted
Order allow,deny
Allow from all
</Directory>
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/risksheet.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/risksheet.com/privkey.pem
Visible Content: Not Found The requested URL /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de was not found on this server. Apache/2.4.29 (Ubuntu) Server at risksheet.com Port 80
Thank you again for your help. I don't understand most of what you reported. I think you are saying I have two certificates when I should have only one. Not sure how remedy that.
Here is the output you requested:
root@risksheet:~# apachectl -S
VirtualHost configuration:
*:443 is a NameVirtualHost
port 443 namevhost risksheet.com (/etc/apache2/sites-enabled/default-ssl.conf:2)
port 443 namevhost www.risksheet.com (/etc/apache2/sites-enabled/risksheet.com-le-ssl.conf:2)
alias risksheet.com
port 443 namevhost www.thebrookhavengroup.com (/etc/apache2/sites-enabled/thebrookhavengroup.com-le-ssl.conf:2)
alias thebrookhavengroup.com
*:80 is a NameVirtualHost
default server risksheet.com (/etc/apache2/sites-enabled/000-default.conf:1)
port 80 namevhost risksheet.com (/etc/apache2/sites-enabled/000-default.conf:1)
port 80 namevhost www.risksheet.com (/etc/apache2/sites-enabled/risksheet.com.conf:1)
alias risksheet.com
port 80 namevhost www.thebrookhavengroup.com (/etc/apache2/sites-enabled/thebrookhavengroup.com.conf:1)
alias thebrookhavengroup.com
ServerRoot: "/etc/apache2"
Main DocumentRoot: "/var/www/html"
Main ErrorLog: "/var/log/apache2/error.log"
Mutex rewrite-map: using_defaults
Mutex ssl-stapling-refresh: using_defaults
Mutex ssl-stapling: using_defaults
Mutex ssl-cache: using_defaults
Mutex default: dir="/var/run/apache2/" mechanism=default
Mutex mpm-accept: using_defaults
Mutex watchdog-callback: using_defaults
PidFile: "/var/run/apache2/apache2.pid"
Define: DUMP_VHOSTS
Define: DUMP_RUN_CFG
Define: ENABLE_USR_LIB_CGI_BIN
User: name="www-data" id=33
Group: name="www-data" id=33
root@risksheet:~#
OK, I did what you said but I don’t know what you did to check and get that Certificate error: RemoteCertficateNameMismatch. But it seems like it is all working.