Apache fails to start after ssl

11,796

Do the following to fix this -

#hostname

This should give your hostname.

Edit the /etc/hosts file and add the following line

your_ip_address your_hostname

Restart apache

Share:
11,796

Related videos on Youtube

frank_texti
Author by

frank_texti

Updated on September 18, 2022

Comments

  • frank_texti
    frank_texti over 1 year

    after installing an ssl cert (using ssl.conf) apache won't restart and only gives these warns in the log:

    [Wed Aug 14 14:16:46 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [Wed Aug 14 14:16:46 2013] [notice] SSL FIPS mode disabled
    

    Using Cent OS 6.4

    Full log (with loglevel debug) :

    [Thu Aug 15 12:54:00 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [Thu Aug 15 12:54:00 2013] [info] Init: Seeding PRNG with 256 bytes of entropy
    [Thu Aug 15 12:54:00 2013] [notice] SSL FIPS mode disabled
    [Thu Aug 15 12:54:00 2013] [info] Init: Generating temporary RSA private keys (512/1024 bits)
    [Thu Aug 15 12:54:00 2013] [info] Init: Generating temporary DH parameters (512/1024 bits)
    [Thu Aug 15 12:54:00 2013] [info] Init: Initializing (virtual) servers for SSL
    

    And STRACES results on paste bin :

    http://pastebin.com/KE4Pe5vF

    • Céline Aussourd
      Céline Aussourd about 10 years
      - Take a look at the content of the virtualhost error log file. - Check that the certificate and the key have the same modulus. / I had the exact same output on the main error_log file. But I also had this error in the virtualhost error file: "Unable to configure RSA server private key" and "certificate routines:X509_check_private_key:key values mismatch". The error was because the private key that was being loaded in the VirtualHost section of the .conf file didn't match the SSL Certificate being loaded in the same section.
    • efesaid
      efesaid about 9 years
      Did you check your private key and certificate? Are they pairing?
  • frank_texti
    frank_texti almost 11 years
    Yeah I did that and also updated servername in httpd conf (this got rid of the httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName error) but still fails to start.