I added three Let'sEncrypt certificates for three domains with their own distinct websites. The certificates show as follows:
Found the following certs: Certificate Name: mydomain1.info Domains: mydomain1.info Expiry Date: 2020-01-08 13:49:13+00:00 (VALID: 89 days) Certificate Path: /etc/letsencrypt/live/mydomain1.info/fullchain.pem Private Key Path: /etc/letsencrypt/live/mydomain1.info/privkey.pem Certificate Name: www.mydomain2.com Domains: www.mydomain2.com mydomain2.com Expiry Date: 2020-01-08 15:12:43+00:00 (VALID: 89 days) Certificate Path: /etc/letsencrypt/live/www.mydomain2.com/fullchain.pem Private Key Path: /etc/letsencrypt/live/www.mydomain2.com/privkey.pem Certificate Name: www.mydomain3.ca Domains: www.mydomain3.ca mydomain3.ca Expiry Date: 2020-01-08 15:12:43+00:00 (VALID: 89 days) Certificate Path: /etc/letsencrypt/live/www.mydomain3.ca/fullchain.pem Private Key Path: /etc/letsencrypt/live/www.mydomain3.ca/privkey.pem
Unfortunately, when I test mydomain2.com or mydomain3.ca on www.ssllabs.com I get the following errors for both
Certificate name mismatch
Try these other domain names (extracted from the certificates): mydomain1.info
The web site does not use SSL, but shares an IP address with some other site that does
Something seems to have a problem identifying the correct certificates.
Why are the respective certificates of mydomain2 and mydomain3 not recognized?
It seems to indicate that LetsEncrypt cannot handle more than one certificate per IP address, although I find that unlikely. I am by no means a Linux administrator, but from what I have researched, I understand that the issue of dealing with multiple domains on a single IP address and even the same port has long been resolved and applies to the versions of the packages installed on my server
There are also errors when I restart httpd indicating a port 443 conflict
[Thu Oct 10 13:54:50 2019] [warn] VirtualHost xx.xxx.xxx.xx:443 overlaps with VirtualHost xx.xxx.xxx.xx:443, the first has precedence, perhaps you need a NameVirtualHost directive [Thu Oct 10 13:54:50 2019] [warn] VirtualHost xx.xxx.xxx.xx:443 overlaps with VirtualHost xx.xxx.xxx.xx:443, the first has precedence, perhaps you need a NameVirtualHost directive
httpd.conf file already contains the NameVirtualHost directive ahead of the < VirtualHost > statements
Any explanations, and especially suggestions on how to correct this issue, are most welcome.
For others who might have the same issues, the port conflict issue was resolved by changing [ip]:80 and [ip]:443 used in the < VirtualHost > and NameVirtualHost directives to *:80 and *.443 and have NameVirtualHost statements for both in the httpd.conf file as follows
NameVirtualHost *:80 NameVirtualHost *:443
Thanks for the feedback to those who responded.