Some of the cheaper or newer SSL suppliers will require this to work properly (otherwise you may be prompted that the cert is invalid when it's not the case but it will certainly scare off your users!).

In the Apache vhost conf for the domain here is what you add:

SSLCACertificateFile /path/to/your/cafile.pem

Here is a full example of an SSL Vhost config in Apache using a CA Certificate file

<VirtualHost *:443>
DocumentRoot /www/vhosts/domain.com/httpdocs
ServerName domain.com
ServerAlias www.domain.com
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" combined
CustomLog /www/vhosts/domain.com/stats/access_log combined
ErrorLog /www/vhosts/domain.com/stats/error_log
#begin enable SSL
SSLEngine on
SSLVerifyClient none
SSLCertificateFile /www/ssl-certs/www.domain.com-ssl-cert.crt
SSLCertificateKeyFile /www/ssl-certs/www.domain.com-ssl-private.key
SSLCACertificateFile /www/ssl-certs/www.domain.com-ssl-ca.crt
#begin stop SSL
</VirtualHost>


installing, ssl, certificate, intermediary, ca, filesome, cheaper, newer, suppliers, prompted, cert, invalid, users, apache, vhost, conf, domain, sslcacertificatefile, cafile, pem, config, virtualhost, documentroot, www, vhosts, httpdocs, servername, serveralias, logformat, quot, referer, user, combined, customlog, stats, access_log, errorlog, error_log, enable, sslengine, sslverifyclient, sslcertificatefile, certs, crt, sslcertificatekeyfile,

Latest Articles