Rewrite test failed

Contents

Overview

Elgg uses clean URLs. This requires rewriting the URLs. If the rewrite test is failing, your server is not configured for rewriting URLs. Below are possible causes and their solution.

No rewrite module

Problem

Some web servers (like Apache) do not have URL rewriting built-in, but instead depend on a module or plugin to be loaded. If the module is not loaded, the web server cannot rewrite the URLs.

Solution

Activate URL rewriting for the web server. How to do this depends on the web server.

Apache will not process the .htaccess file

Problem

The .htaccess file lets you change Apache's configuration on a per directory basis. Elgg uses this file to configure its rewrite rules. If Apache is not configured to read the .htaccess file, the rewrite rules are not loaded.

Solution

The AllowOverride option must be set to All for Apache to process the .htaccess file.

Cannot create the .htaccess file

Problem

Elgg will try to create the .htaccess file in its base directory. If it does not have permission to do that, you will see an error about not being able to create this file.

Solution

You need to either open up the permissions of the base directory or you can copy the htaccess_dist file distributed with Elgg as .htaccess. If you do open up the permissions, please set them back after you are done installing or you will create a security hole.

Installing in a subdirectory

Problem

If you are not installing Elgg into the base of your web directory and if

Solution

Setting the rewrite rules on a web server other than Apache

Problem

Other web servers do not process .htaccess files and need to have the rewrite rules added to their configuration.

Solution

Search docs