[SPLIT] Secure Sentora Login with Let's Encrypt

[worksmarter]

Right on, I will add your findings to the tutorial to help complete the CentOS instructions. I may also set up a CentOS VM and see how that goes, if I can make the time.

I would be more than happy to contribute, but this is behaving badly again. Right after changing the Global Sentora port from 80 to 443 and hit save, it crashed Apache 2.2

This is what Apache is now saying, but I don't know how to proceed.

I am pretty sure you will know how to assist me after looking at the Apache error log. I had no real luck with Google.

Code:

-- resuming normal operations
[Fri Dec 09 06:10:29 2016] [notice] caught SIGTERM, shutting down
[Fri Dec 09 06:17:59 2016] [notice] Digest: generating secret for digest authentication ...
[Fri Dec 09 06:17:59 2016] [notice] Digest: done
[Fri Dec 09 06:17:59 2016] [notice] Apache/2.2.15 (Unix) mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations
[Fri Dec 09 06:20:02 2016] [notice] SIGHUP received.  Attempting to restart
[Fri Dec 09 06:20:02 2016] [notice] Digest: generating secret for digest authentication ...
[Fri Dec 09 06:20:02 2016] [notice] Digest: done
[Fri Dec 09 06:20:02 2016] [error] Server should be SSL-aware but has no certificate configured [Hint: SSLCertificateFile] ((null):0)
[Fri Dec 09 06:21:26 2016] [error] Server should be SSL-aware but has no certificate configured [Hint: SSLCertificateFile] ((null):0)
[Fri Dec 09 06:24:39 2016] [error] Server should be SSL-aware but has no certificate configured [Hint: SSLCertificateFile] ((null):0)
[Fri Dec 09 06:35:02 2016] [error] Server should be SSL-aware but has no certificate configured [Hint: SSLCertificateFile] ((null):0)

You can see in the last entries while I tried to start Apache and get the [failed] response in the cli.

Incidentally this same mystery error, while it appeared all on its own, is what induced me to reinstall fresh - both I need stability as well to have it function. I will search on this error this week end.

Also for more info, my post about breaking Apache on page four would seem to be the same issue. In the end there I had to restore to a backup and then it worked, but it did some automated stuff with the ssl.conf file naming.

Hmm I am wondering what the difference was between the one that worked and this one which was some automated changes to ssl.conf. Looking at ssl.conf says the certificates should be in .pki and such. Could this be the issue and if so, how do we prevent it in the future?