Analyzing Error with Apache2

This customer is receiving an [[an error occurred while processing this directive]] error. This concerns SSI and required more analysis, but this is how I went about it.

I have taken a look at your server and I can see your running apache2 / version 2.2.16

$ curl -I somewebsite.com
HTTP/1.1 301 Moved Permanently
Date: Tue, 02 Feb 2016 17:08:44 GMT
Server: Apache/2.2.16 (Debian)
Location: somewebsite.com
Vary: Accept-Encoding
Content-Type: text/html; charset=iso-8859-1

Although I can’t be certain it looks like there is an issue with the configuration of the apache2, potentially with the moved permanently redirect, but I can’t say for certain from the error message that is given in the html page.

The web page is certainly responding now that the port is state OPEN/ACTIVE though, so we are making progress.

$ curl somewebsite.com


301 Moved Permanently

Moved Permanently

The document has moved here.


Apache/2.2.16 (Debian) Server at somewebsite.com Port 80

It looks like something happens after the redirect/moved permanently.

I would recommend visiting the site and tail’ing the access.log and error.log of your server. this is usually /var/log/apache2/access.log /var/log/apache2/error.log and /var/log/httpd/access.log and /var/log/httpd/error.log, depending on the distribution and configuration this can sometimes be different.

Run something like this:

tail -f /var/log/apache2/error.log

and then load the website up in your browser and observe the errors seen by apache2 on the server, it’s most likely the output will be far more verbose on the backend logs than in the front end error given on the web page.

For more information on SSI (server side includes), please see the apache foundation here (I haven’t discovered exactly where the code is wrong yet and am waiting for customer to give me their virtualhosts configuration/ httpd.conf)

https://httpd.apache.org/docs/2.2/howto/ssi.html
is point, if you require additional assistance we’d benefit from seeing your virtualhosts configuration from within httpd.conf.

Leave a Reply

Your email address will not be published. Required fields are marked *