Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to setup SSL on fedora with apache.

In my vhost...

SSLCertificateFile /your/path/to/crt.crt
SSLCertificateKeyFile /your/path/to/key.key
SSLCertificateChainFile /your/path/to/DigiCertCA.crt

I had it working fine with a self signed key, but can't get it to work with the DigiCertCA crt.

When I run

service httpd restart

It fails to start. This is what I get in the logs...

[Sat Jan 29 07:57:13 2011] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suex$
[Sat Jan 29 07:57:13 2011] [error] Failed to configure CA certificate chain!

Any assistance would be really appreciated!


share|improve this question
up vote 4 down vote accepted

Make sure there's no missing certificates in the chain, in the SSLCertificateChainFile file there should be all the certificates in order from the CA first and then down to any intermediate certificate that was used to sign your CRT, otherwise you'll get the error.

If you don't have any intermediate certificates (looking at the Digicert page it looks like there's none you should use SSLCACertificateFile instead

share|improve this answer
I don't know who downvoted you, this is entirely valid - the instructions even tell you to use SSLCACertificateFile. – troyengel Jan 29 '11 at 15:29
Thanks. turns out it was just there was an 'X' at the bottom of one of the crt files (that I had accidentally put in the file when pressing ctrl+x to close the file. Answer accepted for just checking the chain properly. – kron Jan 29 '11 at 15:56
If you think you copied and pasted correctly double check for white space. For example copying from the Verisign/Symantec the help page… results in two extra spaces on each line. – Daniel Sokolowski Dec 15 '12 at 5:45

The fix above may be useful, but for me the fix was this:

In case the link goes:

The format in this case is p7b (PCKS #7); to use the certificate witih apache you’re going to have to convert this.

openssl pkcs7 -print_certs -in certificate.p7b -out certificate.cer

Within the resulting .cer file you will file you x.509 certificate bundled with relevant CA certificates, break these out into your relevant .crt and ca.crt files and load as normal into apache.

share|improve this answer

An update to an old thread...

I just had this happened when I created a CA chain file by cat-ing the intermediate & root .crt files together into a new .ca-bundle file; the issue was that the first of the cert files didn't end with a newline, so its "END" line and the next one's BEGIN line were joined together, like


I just edited the file and put the newline in, giving:



And then it worked.

share|improve this answer
Good catch and useful caveat. You could use the editor to put the text fragments into "code blocks". – Dan Garthwaite Mar 17 at 14:03

i had similar issue when i copied digicert intermediate certificate while saving the cert i mistakenly entered some characters in the cert file and i couldn't restart apache but when i removed the characters and restarted the server it worked.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.