Magento, how to rewrite index.php in url ? (nginx)

Magento, how to rewrite index.php in url ? (nginx)

July 19, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento, how to rewrite index.php in url ? (nginx)

Solving Magento Index.php Rewrite Issues on Nginx

If you’re facing a 500 internal server error when trying to access a page like domain/indoor.html but can display content with domain/index.php/indoor.html, it’s likely due to an incorrect nginx configuration. Here, I’ll walk you through the steps to properly configure your nginx.conf file for Magento and solve this rewrite issue.

Understanding the Current Configuration

Your current nginx.conf file is set up correctly for most parts, but there are a few areas that might be causing the problem:

# Your existing location block
location ~ .php$ {
    try_files $uri $uri/ =404;
    fastcgi_pass   127.0.0.1:9000;
    # ... other parameters ...
}

The issue lies in the try_files directive. Here, you’re only checking for the existence of the file or directory, but not handling the .php$ matching.

Fixing the Location Block

To properly rewrite requests to index.php, update your location block as follows:

location ~ \.php$ {
    try_files $uri $uri/ /index.php?$args;
}

Here’s what we’ve changed:

  • The regular expression ~ \.php$ matches any file ending in .php.
  • We’ve added a third argument to the try_files directive: /index.php?$args. This tells nginx that if neither the URI nor its directory exists, it should rewrite the request to index.php and pass along the original arguments ($args).

Additional Best Practices

While fixing this specific issue, let’s also implement some other best practices for your Magento configuration:

  1. Enable Compression: Ensure you have gzip enabled in your nginx configuration. This reduces page size and improves load times.
gzip                on;
gzip_vary           on;
gzip_proxied        any;
gzip_types          text/css application/x-javascript;
gzip_buffers        16 8k;
gzip_comp_level     8;
gzip_min_length     1024;
  1. Optimize Image and Script Caching: The existing configuration for images, scripts, and styles is already well-optimized.

  2. Configure FastCGI Parameters: Ensure your fastcgi_pass directive points to the correct PHP-FPM server address and port (usually 127.0.0.1:9000). Also, correctly set SCRIPT_FILENAME.

  3. Enable ETag Header: This helps optimize cache usage on the client side.

add_header ETag "";

Conclusion

With these changes to your nginx.conf file:

  • Update the location block for .php$ files to properly handle rewrites.
  • Implement best practices like gzip compression and optimized image caching.
  • Ensure all FastCGI parameters are correctly configured.

After implementing these updates, restart your nginx service (e.g., sudo systemctl restart nginx), and your Magento rewrite issue should be resolved. You can now access pages like domain/indoor.html without encountering a 500 internal server error.

For further reading on optimizing your Magento performance with nginx, I recommend checking out this comprehensive guide from Laravel Company. It provides detailed insights into configuring nginx for optimal Magento performance.

Configuration Errors

Our network