I followed this tutorial (though it's for 5.2, I figured I'd be alright).
The changes I had to make that seemed to have worked:
- Rename ca.csr to ca.cslr (that's the one the command generated)
- List it in the ssl.conf as ca.cslr instead of ca.csr
I have the following in the httpd.conf
<VirtualHost *:80> DocumentRoot /etc/test ServerName site.com </VirtualHost> <VirtualHost *:433> SSLEngine on SSLCertificateFile /etc/pki/tls/certs/ca.crt SSLCertificateKeyFile /etc/pki/tls/private/ca.key <Directory /etc/test> AllowOverride All </Directory> DocumentRoot /etc/test ServerName cryptokings.com </VirtualHost>
/test contains a folder inside of it, accessible via
http://site.com/test/foo, however attempting to access it via https://site.com/test/foo results in
- warning that the certificate is untrusted (self-signed, no biggie)
- a 404 error.
Chrome's complains about the certificate are the following:
The identity of this website has not been verified. • Server's certificate does not match the URL. • Server's certificate is not trusted.
I think those warnings are a side-effect of a self-signed certificate - or is the first one something that needs to be addressed?
I seem to be able fetch the root page via https just fine though, it shows a standard CentOS setup page. (That said, I haven't added a VirtualHost entry for it so I suppose that makes sense)
I think I've made a mistake somewhere during the setup as I'm not too familiar with the process.
During setup, I was prompted for a type of password that would be required when apache restarts but running
service httpd restart does not seem to prompt me for one.
Any help would be appreciated.