index.php not found in url of cloned Magento Site on Development server?

index.php not found in url of cloned Magento Site on Development server?

August 10, 2026 · Illustrated author avatarBy Stefan Bogdanescu
index.php not found in url of cloned Magento Site on Development server?

Solving the “index.php not found” Issue on Magento Development Servers

Are you facing trouble with your cloned Magento site not loading correctly on your development server? Let’s dive into solving this common issue.

Understanding the Situation

You’ve successfully cloned a Magento 1.5.0.0 site onto your Windows WAMP server, but you’re experiencing URL problems. The index.php file is present and can be loaded manually, yet clicking on pages like “Contact Us” results in a “404 Not Found” error.

Diagnosing the Issue

The problem lies in how the URLs are being generated and handled by your server:

The requested URL /vhosts/petextra/magento/index.php was not found on this server.

Notice that the URL lacks the index.php file. This means that either Magento isn’t generating URLs correctly or your web server configuration is preventing it from doing so.

Potential Causes and Solutions

1. Incorrect Base URL Configuration

Check if you’ve configured the base URL in your database:

SELECT * FROM core_config_data WHERE path LIKE 'web/unsecure/base_url' OR path LIKE 'web/secure/base_url';

The base_url should point to your development server, e.g., http://127.0.0.1/petextra/.

2. Missing or Misconfigured .htaccess File

While you mentioned copying an .htaccess file from another Magento site, double-check if it’s correctly configured and not blocking access to the index.php file.

Ensure your .htaccess file contains directives like these:

RewriteEngine On
RewriteBase /magento/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /magento/index.php [L]

If you’re still having trouble, try creating a new Magento site and copying the .htaccess file from the new installation.

3. Incorrect Document Root Setting

In your Apache configuration (httpd.conf or httpd-vhosts.conf), ensure the document root for your vhost is set correctly:

<VirtualHost *:80>
    ServerName petextra.local
    DocumentRoot "C:/wamp/www/petextra/magento"
</VirtualHost>

The path should end at the folder containing the index.php file.

Debugging and Verifying

After making changes, restart your Apache server to apply them. Then:

  1. Access your site using the base URL (e.g., http://petextra.local/).
  2. Click on a page link like “Contact Us” or manually enter /contact-us/.
  3. Observe the browser address bar and check if it includes index.php.

Conclusion

Resolving this issue usually involves a combination of correctly configuring your base URL in the database, verifying your .htaccess file syntax, and ensuring your document root is set properly.

Remember that development environments often require specific configurations to mimic the live server’s behavior. Always double-check your settings against the original live site’s configuration.

If you’re still facing problems or need further assistance, don’t hesitate to reach out to our support team at Laravel Company. We’d be happy to help troubleshoot this issue for you.

Magento 1 Database Configuration Errors

Our network