Front controller reached 100 router match iterations, cannot access Magento admin panel

Front controller reached 100 router match iterations, cannot access Magento admin panel

September 10, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Front controller reached 100 router match iterations, cannot access Magento admin panel

Solving Magento Admin Panel Access Issues: A Detailed Guide

If you’re facing difficulties accessing your Magento admin panel while your frontend is functioning perfectly, don’t worry—you’re not alone. This issue often occurs due to router configuration problems or misconfigured routing rules. Let’s dive into the error message you provided and find a solution step-by-step.

Understanding the Error Message

The error message Front controller reached 100 router match iterations indicates that Magento has tried multiple times to determine which route should handle the request for your admin panel, but failed after reaching its maximum attempt limit. This usually happens when:

  • Your .htaccess file is not properly configured.
  • The base URL in your core_config_data table is incorrect or empty.
  • Your router configuration is misconfigured.

Step 1: Verify Your Base URL Configuration

The first step is to ensure that the web/unsecure/base_url and web/secure/base_url fields in your core_config_data table are correctly configured. Log into your database using PHPMyAdmin or any other preferred tool, locate this table, and check these two fields.

Here’s an example of what they should look like:

SELECT * FROM core_config_data WHERE path IN ('web/unsecure/base_url', 'web/secure/base_url');

The value column for both paths should contain the correct absolute URL to your store (e.g., https://yourdomain.com).

Step 2: Check Your .htaccess File

Next, navigate to the root directory of your Magento installation and open the .htaccess file. Ensure that it contains the following lines at the top:

# Use mod_rewrite for pretty URLs
<IfModule mod_rewrite.c>
    RewriteEngine on

    # Remove index.php from URLs
    RewriteBase /magento/
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} !(\?.*)?$
    RewriteRule . /index.php [L]
</IfModule>

The RewriteBase line should match your actual Magento installation directory. In this case, it’s set to /magento/.

Step 3: Adjust Your Router Configuration

If the above steps don’t resolve the issue, you might need to adjust your router configuration in the app/code/core/Mage/Core/etc/config.xml file.

Search for the <router> element and ensure that the standard router module is enabled:

<config>
    <modules>
        <Mage_Core_Controller_Varien_Router_Standard>
            <active>true</active>
        </Mage_Core_Controller_Varien_Router_Standard>
    </modules>
</config>

Step 4: Disable Custom Routing Extensions

Sometimes, custom routing extensions or plugins can interfere with Magento’s built-in routing mechanism. If you have any third-party routing extensions installed, temporarily disable them and see if the issue persists.

Conclusion

In most cases, updating your base URL configuration, verifying the .htaccess file, and adjusting router settings should resolve the Front controller reached 100 router match iterations error. Remember to always backup your files before making any changes.

If you still encounter issues after following these steps, consider seeking professional assistance or checking the official Magento documentation for further guidance on resolving routing problems.

For more in-depth tutorials and best practices related to Magento development and troubleshooting, visit Laravel Company blog. We regularly publish articles covering various aspects of eCommerce development with a focus on Laravel and related technologies.

Database Admin Configuration Errors

Our network