(11-20-2016, 06:26 AM)TGates Wrote: Ok, check your httpd-vhosts.conf for Listen 443 and also check httpd.conf for Listen 443
If it is in your httpd-vhosts.conf, comment it out in the httpd.conf
ssl.conf should be disabled by default after a fresh install. It is not used in any of the tutorials either since we use custom vhost entries or custom files in the tutorials.
OK... I restored to a pre-failure backup. What follows is likely the cause of all the problems. You unkowingly are telling CentOS 6.x users to install the ssl.conf file.
Code:
Ok, check your httpd-vhosts.conf for Listen 443 and also check httpd.conf for Listen 443
Nope not contained in either of those files...
Code:
If it is in your httpd-vhosts.conf, comment it out in the httpd.conf
Nope not there either...
You should change your tutorial either with the proper instructions for CentOS, or simply don't say it is compatible only with switching apt-get's for yum and apache2's for httpd - this is not the case.
Installing mod_ssl on CentOS 6.x creates the file ssl.conf in this address. --->
Code:
/etc/httpd/conf.d/ssl.conf
Now I am screwed as I used up all of my privileges at Let'sEncrypt. FYI to others, while I can and will write a working procedure for CentOS 6.x, I cannot even attempt it for I believe ten days of waiting??? Hopefully fellow CentOS users read this after the tutorial and don't end up loosing the services of Let'sEncrypt as I did.
Until I am able to address and correct this problem when Let'sEncrypt will allow me to register the panel/domain again, I would highly recommend no one using CentOS 6.x follow the outlined procedure in post Forum Add-ons and Usage until I or someone else can address this and get a proper procedure.
Thank you for trying to assist TGates.
Everyone makes mistakes, but to truly screw up it takes the root password!