Bottom line for CentOS 6.x (and likely Ubuntu)
You MUST INSTALL mod_ssl as well as openssl - openssl does not mandate the install of mod_ssl in CentOS 6.x.
A) This should be your command in CentOS - (use apt-get for Ubuntu):
B) No if and or buts about it. ssl.conf at this location "/etc/httpd/conf.d" ssl.conf WILL have Listen 443 in it that MUST BE COMMENTED OUT THERE!
If you do this along with TGates procedures, be them for the panel, or a domain you should have success. I can post back after I test a cert on a new domain, but for now this is based on just securing the panel; the topic of this thread.
Although I would not be shocked to have to revisit this while securing domains, but since this is done during the install of mod_ssl - I would like to think the other procedure does not over-write the ssl.conf file - but that is a fight for a new day and different guide... But I have not followed that guide yet, so if you are trying to secure a site first and you install openssl and mod-ssl, you will likely be facing the same issue. TGates, maybe in this and/or the other guide should we be telling people to expect this behavior of Apache breaking down and tell them from the get go they will need to modify their ssl.conf no matter what??? Your call Sir.
You MUST INSTALL mod_ssl as well as openssl - openssl does not mandate the install of mod_ssl in CentOS 6.x.
A) This should be your command in CentOS - (use apt-get for Ubuntu):
Code:
yum install mod_ssl opensslB) No if and or buts about it. ssl.conf at this location "/etc/httpd/conf.d" ssl.conf WILL have Listen 443 in it that MUST BE COMMENTED OUT THERE!
If you do this along with TGates procedures, be them for the panel, or a domain you should have success. I can post back after I test a cert on a new domain, but for now this is based on just securing the panel; the topic of this thread.
Although I would not be shocked to have to revisit this while securing domains, but since this is done during the install of mod_ssl - I would like to think the other procedure does not over-write the ssl.conf file - but that is a fight for a new day and different guide... But I have not followed that guide yet, so if you are trying to secure a site first and you install openssl and mod-ssl, you will likely be facing the same issue. TGates, maybe in this and/or the other guide should we be telling people to expect this behavior of Apache breaking down and tell them from the get go they will need to modify their ssl.conf no matter what??? Your call Sir.
Everyone makes mistakes, but to truly screw up it takes the root password!
