I've tried to solve the following error message through many ways - including setting persmission, etc - but still getting the same message.
Error Message during Install: "The rewrite test failed and the most likely cause is that AllowOverride is not set to All for Elgg's directory....."
Has anyone found the solution for this problem?
I've also encountered this in my environment (using Oracle Virtualbox running a guest Debian LAMP server, sharing the /var/www filesystem, i.e. the web root, with the Win7 host). There was no apparent reason as what could have caused the problem - .htaccess was there, AllowOverride was set to all, file system was writable. I ended up "fixing" the issue with a little hack: I manually stepped over this check and forced the installer to go to the next step. I'm using my 1.8.* sites with no problem since this hacky installation.
So when you hit this wall, simply enter the next installation step's url in your browser: http://your-site-url/install.php?step=database
I understand this is far from a proper solution, but worked for me. Hope it helps you.
I had the same problem with my host/server. This seems to happen with Ubuntu server. Try turning AllowOverride to ALL. If you can't do that for some reason, turn ElggRerwiteTest off in ...install/ElggRewriteTest.php.
That should get you past the rewrite test, after which you'll find a link to test it... if you get a page after with "success" rewrite is enabled.
That's how I got past it with my host who run ubuntu server.
Hope this helps
Same behaviour in my Debian install:
Apache virtual hosting:
Options Indexes FollowSymLinks MultiViews
allow from all
CustomLog /var/log/apache2/access_elgg.log combined
.htaccess created by install process
RewriteBase / line uncommented in .htaccess file
desperate chmod 777 at /path/to/elgg-1.8.3 directory
no way, know issue in install.php?step=requirements
The rewrite test failed and the most likely cause is that AllowOverride is not set to All for Elgg's directory... etc.
somebody knows what am I doing wrong?
thanks in advance.
Solved for me.
while i was receiving "success" from calls to http://elgg.domain.org/rewrite.php, checking response from curl in runRewriteTest function (ElggRewriteTester.php) it was 404!
aha, adding entry xxx.xxx.xxx.xxx elgg.domain.org to my /etc/hosts solved the issue!!
hope this helps.
Strangely, I found that having Basic authentication (a user/pass curtain) set up on the site prevented the rewrite check from working. Surely there's a better way to test than actually making an HTTP request? Or, if that has to be done, allow the user to provide the username and password. I suppose this isn't the place for this suggestion...I'm new so not sure where that is! :)
finally, i found the correct solution:
make sure you first enable mod_rewrite by using the following command:
sudo a2enmod rewrite
After enabling mod_rewrite
change AllowOverRide None in /etc/apache/sites-available/default to AllowOverRide All. Apache won’t read the rewrite rules nor the .htaccess-files if AllowOverRide is set to None.
Security issues should be reported to email@example.com!