magento 2 upgrade to 2.1.3

magento 2 upgrade to 2.1.3

September 23, 2026 · Illustrated author avatarBy Stefan Bogdanescu
magento 2 upgrade to 2.1.3

Resolving Magento 2 Store Not Found Error After Upgrade

You’re not alone if you’ve encountered a store not found error after upgrading your Magento 2 site from version 2.0.11 to 2.1.3. This issue often arises due to changes in the database schema or configuration file during the upgrade process.

Understanding the Store Not Found Error

The Requested store is not found error typically occurs when the system fails to locate a valid website setup during initialization. This could be due to missing or corrupted configuration data, incorrect security settings, or a mismatch between your app/etc/config.php file and the database.

Troubleshooting Steps for Magento 2 Upgrades

Step 1: Verify Your Composer Installation

Before proceeding with any further troubleshooting, let’s ensure that your composer installation is up-to-date. Run these commands in your terminal:

composer global require "lakshyasrivastava/composer-dump-autoload=dev-master"
composer dump-autoload

This will update the autoloading mechanism and ensure that all dependencies are properly loaded.

Step 2: Check Your Configuration Files

Next, let’s inspect your app/etc/config.php file to verify that it contains valid store configuration data. Look for an array of websites under the 'websites' key:

'websites' =>
array (
  'base' =>
  array (
    // ... other settings
    'code' => 'base',
    // ... other settings
  ),
),

Make sure that each website has a unique code and is properly configured.

Step 3: Inspect Your Database

Check the core_store table in your Magento database for any discrepancies. Ensure there are no duplicate entries or incorrect data:

SELECT * FROM core_store WHERE code = 'base';

The query should return exactly one record for your base store with a valid status of ‘enabled’.

Step 4: Re-index and Re-deploy Your Code

Sometimes, the cache can become corrupted during an upgrade. To resolve this issue, try re-indexing and redeploying your code:

php bin/magento indexer:reindex
php bin/magento setup:upgrade
rm -rf var/di var/generation
php bin/magento cache:flush

Step 5: Verify Your Security Settings

Ensure that your security settings are configured correctly in app/etc/config.php:

'system' =>
array (
    // ... other settings
    'web' =>
    array (
        'secure' =>
        array (
            'use_apache2' => 0,
            'use_ssl' => 1,
            'use_ssl_admin' => 1, // Ensure this is set to 1 for the admin panel as well
            'use_ssl_sys' => 0,
        ),
    ),
),

The use_ssl and use_ssl_admin settings should be enabled if you are using SSL.

Seeking Professional Help

If you’ve followed these troubleshooting steps and are still encountering issues, it’s recommended to seek help from a Magento developer or support team. At Laravel Company, we specialize in Magento 2 development and can assist with your upgrade needs: https://laravelcompany.com/services/magento-2-development/

Remember that upgrading to a new version of Magento often requires careful planning and testing. Always backup your data and test the upgrade in a staging environment before deploying it to your live site.

By following these guidelines, you should be able to successfully resolve the store not found error after upgrading your Magento 2 site. If you continue to experience difficulties, don’t hesitate to reach out to our expert team for personalized assistance with your e-commerce platform.

Magento 2 Database Security Configuration

Our network