Magento – Magento 1.9 admin showing 403 forbidden error

magento-1.9

magento front part is working fine but magento admin panel showing 403 error.

Forbidden

You don't have permission to access /agluser on this server.
Apache/2.4.18 (Ubuntu) Server at www.aglasiangranito.com Port 443

any suggestion or help is highly appreciated.

thnks

Best Answer

go to your Database Management:

Open PhpMyAdmin
Go to your database
Click SQL
Run the following SQL Query

SET FOREIGN_KEY_CHECKS=0;
UPDATE `core_store` SET store_id = 0 WHERE code='admin';
UPDATE `core_store_group` SET group_id = 0 WHERE name='Default';
UPDATE `core_website` SET website_id = 0 WHERE code='admin';
UPDATE `customer_group` SET customer_group_id = 0 WHERE customer_group_code='NOT LOGGED IN';
SET FOREIGN_KEY_CHECKS=1;

Related Solutions

Magento Extension Not Showing in Admin Panel – Fix for Magento 1.9

In addition to @Talesh explanation I would like to mention something that was driving me crazy long ago and I recently saw again: Make sure that the file name in app/etc/modules/[Namespace]_[Module].xml match the namespace and module in

  <?xml version="1.0"?>
    <config>
        <modules>
            <[Namespace]_[Module]> <!-- Equal to this -->
              ...
            </[Namespace]_[Module]>
        </modules>
    </config>

Same goes for the the configuration file in app/code/[codePool]/[Namespace]/[Module]/etc/config.xml and its content

<?xml version="1.0"?>
<config>
    <modules>
        <[Namespace]_[Module]>
            <version>1.0.0</version>
        </[Namespace]_[Module]>
    </modules>
    ...

Pay special attention to capitals and lowercase characters in files and folders name as well as module configuration and declaration files. In all cases they need to match. Hope it helps

Magento – 403 forbidden error while POST content – Nexcess server

You may have triggered some Mod Security rules with your custom module.

Try checking your Mod Security logs or disable it and see if it works.

If it's confirmed to be caused by Mod Security, you can either identify the particular rule and disable it or change your codes to workaround the rule.

Best Answer

Related Solutions

Magento Extension Not Showing in Admin Panel – Fix for Magento 1.9

Magento – 403 forbidden error while POST content – Nexcess server

Related Topic