Apache SSL Certificate Installation

1) Copy the Certificate files to your server

Download your Intermediate (DigiCertCA.crt) and Primary Certificate (your_domain_name.crt) files from your Customer Area, then copy them to the directory on your server where you will keep your certificate and key files. Make them readable by root only.

2) Find the Apache config file to edit:

The location and name of this file can vary from server to server -- Especially if you use a special interface to manage your server configuration.

Apache configuration files are typically found in /etc/httpd. The main configuration file is usually named httpd.conf. In some cases the <VirtualHost> blocks will be at the bottom of this httpd.conf file. Sometimes you will find the <VirtualHost> blocks in their own files under a directory like /etc/httpd/vhosts.d/ or /etc/httpd/sites/ or in a file called ssl.conf.

If you open the file with a text editor, you should be able to find <VirtualHost> blocks which contain Apache settings.

3) Identify the SSL <VirtualHost> block to configure:

If you need your site to be accessible through both secure (https) and non-secure (http) connections, you will need a virtual host for each type of connection. Make a copy of the existing non-secure virtual host and configure it for SSL as described in step 4.

If you only need your site to be accessed securely, configure the existing virtual host for SSL as described in step 4.

4) Configure the <VirtualHost> block for the SSL-enabled site:

Below is a very simple example of a virtual host configured for SSL. The parts listed in bold are the parts that must be added for SSL configuration:

<VirtualHost 192.168.0.1:443>
    DocumentRoot /var/www/html2
    ServerName www.yourdomain.com
    SSLEngine on
    SSLCertificateFile /path/to/your_domain_name.crt
    SSLCertificateKeyFile /path/to/your_private.key
    SSLCertificateChainFile /path/to/DigiCertCA.crt
</VirtualHost>

Adjust the file names to match your certificate files:

• SSLCertificateFile should be your DigiCert certificate file (eg. your_domain_name.crt).
• SSLCertificateKeyFile should be the key file generated when you created the CSR.
• SSLCertificateChainFile should be the DigiCert intermediate certificate file (DigiCertCA.crt)

5) Test your Apache config before restarting.

It is always best to check your Apache config files for any errors before restarting, because Apache will not start again if your config files have syntax errors. Run the following command: (it is apache2ctl on some systems)

apachectl configtest

6) Restart Apache.

You can use apachectl commands to stop and start Apache with SSL support:

apachectl stop
apachectl start

Note: If Apache does not start with SSL support, try using "apachectl startssl" instead of "apachectl start". If SSL support only loads with "apachectl startssl" we recommend you adjust the apache startup configuration to include SSL support in the regular "apachectl start" command. Otherwise your server may require that you manually restart Apache using "apachectl startssl" in the event of a server reboot. This usually involves removing the <IfDefine SSL> and </IfDefine> tags that enclose your SSL configuration.

7) Test your SSL site with a browser.

For best results exit your web browser first and then re-launch it. Go to your site using its https secure URL. Test with more than just Internet Explorer because IE is able to permanently cache intermediate SSL certificates, so IE will sometimes appear fine even though Firefox and other browsers will give a trust warning.

If your site is public, you can also use our Server Certificate Tester which can detect common problems.

Troubleshooting tips:

If you receive a "not trusted" warning, view the certificate to see if it is the certificate you expect. Check the Subject, Issuer, and Valid To fields. If the certificate is issued by DigiCert, then your SSLCertificateChainFile is not correctly configured.

If you do not see the certificate you expect then you may have another SSL <VirtualHost> block before the one you recently configured. Name based virtual hosts are not possible with https unless you use the same certificate for all virtual hosts (eg. a wildcard certificate, or a unified communications certificate) It is not a limitation of Apache, but of the SSL protocol. Because Apache must send a certificate during the SSL handshake, before it receives the HTTP request which contains the Host header, Apache always sends the SSLCertificateFile from the first <VirtualHost> block that matches the ip and port of the request.