If apache server failed to restart like this :

sudo service httpd restart
Stopping httpd: [FAILED]
Starting httpd: [FAILED]

then you need to check error logs which might be under this directory if you are running CentOS:


inside this directory you will see error_log. Open this file and read last few entries with:

trail -100 error_log

and if you spot that last few entries are like this :

[Fri Apr 14 19:59:25 2017] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)

Then probably you have mis-configured your ssl.conf file or its got corrupted. This file can be under directory:


now to fix this error you need to rename your existing ssl.conf file with mv command:

mv ssl.conf ssl.conf.old

and then create one new ssl.conf and put the defaults contents in it from this comment:

or download from attached post and rename from ssl.conf.txt to ssl.conf and save it on your server.

and press :wq to save and quit.

Now restart your apache server to see if problem is gone:

sudo service httpd restart

Stopping httpd: [ OK ]
Starting httpd: [ OK ]

Run following on Linux terminal :

ps -ef | grep apache

which will yield the result like

root  3753   1  0 Jul12 ?    00:00:19 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf

The last parameter above ( /etc/apache2/httpd.conf) will show the apache directory and the path of httpd.conf .

Apache Server log Locations on different linux flavours :

RHEL / Red Hat / CentOS / Fedora Linux Apache error file location - /var/log/httpd/error_log
Debian / Ubuntu Linux Apache error log file location - /var/log/apache2/error.log
FreeBSD Apache error log file location - /var/log/httpd-error.log

On most webservers, this means that would show a listing of the directory's contents. But showing that directory is forbidden by server configuration

To solve this you have to find the .htaccess or httpd.conf file in your root and edit the following :

Options -Indexes

with :

Options +Indexes

to allow proper listing of files.

Subscribe to RSS - Apache