This guide assumes that you have already installed Apache2.2 and OpenSSL on your server.

Once you have gotten the certificate file back from your CA, you will want to rename the certificate file to your commonname.cert.

You will then go to:

C:\Program Files\Apache Foundation Software\Apache2.2\conf

and create a directory called ‘ssl’. Then go into the directory:

C:\Program Files\Apache Foundation Software\Apache2.2\conf\ssl

Copy your *.key file and *.cert file into this directory. We then have to make changes to the httpd.conf file. You will need to add a few lines. The first will go towards the bottom of the configuration file before anyorentries. The lines are:

 

Include conf/ssl.conf

Then you will want to browse to:

C:\Program Files\Apache Foundation Software\Apache2.2\conf\extra

and locate the httpd-ssl.conf file. Copy this into your:

C:\Program Files\Apache Foundation Software\Apache2.2\conf

directory and rename this to ssl.conf. In both the httpd.conf and ssl.conf, locate the lines:

ServerName

and make sure that they are formated as:

httpd.conf
ServerName commonname:80

ssl.conf
ServerName commonname:443

In the ssl.conf file, locate the following variables: SSLCertificateFile and SSLCertificateKeyFile. You will need to point these to the location of your *.cert and *.key. They should look like:

SSLCertificateFile C:/Program Files/Apache Foundation Software/Apache2.2/conf/ssl/commonname.cert

SSLCertificateKeyFile C:/Program Files/Apache Foundation Software/Apache2.2/conf/ssl/commonname.key

Save all your files, and start Apache from Start > Run > services.msc. All things being, this should work and you should be able to go to a command prompt and type in the following:

telnet localhost 80

and

telnet localhost 443

and each should return a blank screen with a blinking curser in the upper left corner. If you get any errors, make sure to check the Event Viewer > Application to see what Apache is reporting as being a problem. Also within the directory:

C:\Program Files\Apache Foundation Software\Apache2.2\log

there is an error.log file that will log out any errors that you might have.

Also you can also check your installation by going to Verisign’s Checker tool.

Known Issue 1

There is one know issue on Windows, if you get the error message in the error.log as:

Error: Init: SSLPassPhraseDialog builtin is not supported on Win32

This is because a password was entered while generating the key file via openssl. To fix this, you will first need to go to the ssl.conf file and comment out the line that contains:

SSLPassPhraseDialog

and save the file. Then you will want to go to your directory:

C:/Program Files/Apache Foundation Software/Apache2.2/bin

and run the following command:

openssl rsa -in commonname.key -out commonname2.key

Copy the commonname2.key file and then go to:

C:/Program Files/Apache Foundation Software/Apache2.2/conf/ssl

and delete the current commonname.key and replace it with commonname2.key. Rename commonname2.key to commoname.key.

Try to restart Apache from Start > Run > services.msc and see if that works for you!

Known Issue 2

If you are using a Verisign SSL Certificate, you may have a experienced a problem where pulling up the secure site will return an error indicating: Unable to verify the identify of commonname as a trusted site.

This is because with Verisign certificates, you now need to install an intermediate certificate. That can be found directly from Verisign. The key is that within the ssl.conf file you need to uncomment out the line:

SSLCertificateChainFile “C:/Program Files/Apache Software Foundation/Apache2.2/conf/ssl/intermediate.crt”

save, then restart Apache. Keep in mind that the name there is what you save the intermediate certificate that you get from the Verisign site, make sure that you save the file name in the ssl directory.

Once you do this, your cert should work fine. Use the Verisign checker to verify your findings.

Reference
Reference
Reference