Apache changing AllowOverride made my server fail

Posted on

Apache changing AllowOverride made my server fail – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.

But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about linux, apache-2.2, , , .

http://ec2-54-243-158-66.compute-1.amazonaws.com

I was following a tutorial and right after I did this, my server stopped responding:

sudo su

vi /etc/httpd/conf/httpd.conf

find the line:
AllowOverride None – after the (about line 339 or so…)

change to AllowOverride All (case matters! All not all or ALL)

:wq to save

service httpd restart

I reverted everything back to exactly what it was and it still wont work.

Edit: http://stephen-white.blogspot.com/2012/05/how-to-set-up-wordpress-on-amazon-ec2_31.html This was the tutorial I was following, everything worked until I made that change suggested by a comment at the bottom that allowed wordpress to modify the .htaccess for permalinks

Solution :

Hopefully you have figured this out by now, but I will share a very helpful command:
httpd -S
This will syntax check your configuration files for you. It may give you a clue as to why apache will not start. The /var/log/httpd/error_log should also have helpful information.

Leave a Reply

Your email address will not be published.