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.
VirtualHost configuration:
*:80 is a NameVirtualHost
default server envirotemps.com (/usr/local/etc/httpd/extra/httpd-vhosts.conf:30)
port 80 namevhost envirotemps.com (/usr/local/etc/httpd/extra/httpd-vhosts.conf:30)
alias www.envirotemps.com
port 80 namevhost Hi-Tech.Rent (/usr/local/etc/httpd/extra/httpd-vhosts.conf:58)
alias www.Hi-Tech.Rent
port 80 namevhost D7036.com (/usr/local/etc/httpd/extra/httpd-vhosts.conf:85)
alias www.D7036.com
port 80 namevhost walkershire.net (/usr/local/etc/httpd/extra/httpd-vhosts.conf:110)
alias www.walkershire.net
port 80 namevhost Hi-TechRent.com (/usr/local/etc/httpd/extra/httpd-vhosts.conf:136)
alias www.Hi-TechRent.com
port 80 namevhost beyond.cleanair.com (/usr/local/etc/httpd/extra/httpd-vhosts.conf:163)
alias www.beyond.cleanair.com
port 80 namevhost www.remiwalker.com (/usr/local/etc/httpd/extra/httpd-vhosts.conf:221)
alias remiwalker.com
port 80 namevhost 70.89.220.117 (/usr/local/etc/httpd/extra/httpd-vhosts.conf:276)
port 80 namevhost localhost (/usr/local/etc/httpd/extra/httpd-vhosts.conf:322)
*:443 localhost (/usr/local/etc/httpd/extra/httpd-ssl.conf:121)
The names are only individualized within the HTTP server blocks.
There is only one HTTPS server block [and it serves all the sites from a root to all of them].
That means: http://envirotemps.com works https://envirotemps.com fails http://Hi-Tech.Rent works https://Hi-Tech.Rent fails
...
You will need to make individualized HTTPS server blocks [one for each of the names].
So that each name can be pointed to the corresponding DocumentRoot.
But the first step is to ensure you have a cert for each of the names.
Let's have a look at: certbot certificates
For brevity, I will refer to the certs by their order of appearance.
All cert #1 names are covered by cert #5
The cert #2 name is covered by cert #5
The cert #3 name is covered by cert #5
The cert #4 name is covered by cert #5
So, you really only need cert #5.
You can delete the first four certs, with: certbot delete --cert-name beyond.cleanair.com certbot delete --cert-name d7036.com certbot delete --cert-name envirotemps.com certbot delete --cert-name hi-tech.rent
OR you could go in the completely opposite direction and obtain individualized certs [one per name].
For that, delete the first and last certs and then obtain new ones with only the individual names on them.
That said, none of the certs cover any of the "www" names.
[which is what I think you were referring to]
OK, so required cert(s):
Next step: Create HTTPS server blocks for each site/name.
That is a very basic Apache "how to" type question that isn't really part of what we try to cover here.
That said, certbot can take an HTTP server block and make an HTTPS server block from it.
So, you could use certbot to get them all going [at least with a basic config] for you.
I temporarily solve my problem by using this in my http-VHosts.config
Options +FollowSymLinks
RewriteEngine On
RewriteCond %{ENV:HTTPS} !=on
RewriteRule ^(.*)$ https://walkershire.net/walkershire$1 [R=301,L]
This is causing your server to send duplicate leaf certs
Replace cert.pem with with fullchain.pem and remove the line for SSLCertificateChainFile. This latter option was deprecated long ago and is only used in very peculiar cases. So, should be:
