How to Fix 404 Error Page Not Found in Magento 2 Admin Pages

Just installed Magento 2 Extensions, and saw the annoying 404 Error Page Not Found in your admin pages? Don’t worry! This is a common issue caused by session permissions. In this simple guide, we’ll explain the top 4 reasons why this happens—it could be due to a Magento 2 installation problem, an extension upgrade, a 403 Forbidden error, or a messy page. Plus, we’ll give you easy steps to fix the 404 Error Page Not Found and get your admin pages working again. Let’s get started and solve it!

Related Topics:

• Configure Full Page Cache
• 10 Cache Types: How to Manage Cache
• Service Temporarily Unavailable
• Exception printing is disabled by default for security reasons
• You Don’t Have Permission To Access / On This Server

4 problems why Magento 2 404 Error Page Not Found in Admin

Here are 4 reasons why you get a 404 Error Page Not Found in the backend and guidance on how to solve them. Please, follow the steps to learn how to deal with the issue of each case.

• Problem 1: After installing/upgrading
• Problem 2: Fresh Install On Ubuntu/Centos/Debian
• Problem 3: Page 403 Forbidden errors
• Problem 4: Messy page, no style
• Problem 5: A change starting from Magento 2.4.2

Problem 1: After installing/upgrading

Description: You may get the error in cases of:

• After installing a new extension
• After upgrading extensions
• After applying patches of Magento core or extensions.

Solution:

Flush Magento Cache with command line:

php bin/magento cache:clean
rm -rf var/cache/*
rm -rf var/generation/*

Read How to flush Magento 2 cache for more details.

• Flush cache in Admin: Admin > Systems > Cache Management
• Log out then login again

Case: 404 Error Page not found error on extension admin route update Installing SUPEE - 6788

Try to contact the extension provider for more details.

Problem 2: Fresh Install On Ubuntu/Centos/Debian

Description: After installation on Ubuntu/Centos/Debian, this error may be shown like this:

Why?

It’s because your server does not enable rewrite mode.

Solution

1. Enable Rewrite mode

sudo a2enmod rewrite

1. Configure apache

For Ubuntu / Debian edit the file /etc/apache2/apache2.conf. To edit this file, you can run command

sudo vi /etc/apache2/apache2.conf 

Modify from:

<Directory /var/www/>
     Options Indexes FollowSymLinks
     AllowOverride None
     Require all granted
</Directory>

to

<Directory /var/www/>
    Options Indexes FollowSymLinks
    AllowOverride All
    Require all granted
</Directory>

Then restart apache

sudo service apache2 restart

or

sudo /etc/init.d/apache2 restart

1. If the admin still displays a 404 error, take the following steps:

a, Place the .htaccess file from the root of Magento 2

b, Execute the following commands:

• php bin/magento setup:upgrade
• php bin/magento setup:static-content:deploy
• rm -rf var/cache/*
• rm -rf var/generation/*

Problem 3: Page 403 Forbidden errors

If you are experencing with 403 Forbidden errors while accessing to Magento store, you should update Apache configuration to allow visitors access to your site.

Solution

• Open apache2.conf file
• For Ubuntu, the file /etc/apache2/apache2.conf. To edit this file run command

sudo vi /etc/apache2/apache2.conf 

Update like this:

<Directory /var/www/>
	Options Indexes FollowSymLinks MultiViews
	AllowOverride All
	Order allow,deny
	Allow from all
</Directory>

Problem 4: Messy page, no style

Description: As shown in the below image, a messy frontend may occur, leading to the 404 error in the backend.

Why?

There are 2 cases:

• You server does not enable rewrite mode, try this solution
• Deploy static content: follow the below solution.

Solution

It is because the static content is not generated to the pub/ folder. Let’s run this command to deploy it. Please try to run the following command:

php bin/magento setup:static-content:deploy

Problem 5: A change starting from Magento 2.4.2

Description

This fix is for people using Magento version 2.4.2 and newer. If you see a 404 error after installing Magento 2.4.2, it’s because of a change in Magento 2.4.2.

Solution

You need to set the webroot to /pub/ to enhance security. To solve this, follow Magento’s official guide. It includes steps like changing server settings, updating the base URL, changing the env.php file, and switching modes.

The bottom line

These are 4 main causes and solutions for the 404 error Page Not Found in Magento 2. It is an annoying but quite common error, so as long as you are well aware of the reason, you can quickly fix the problem. If you find any other problem or want to discuss further, feel free to write in the comment box.

What about Magento 2 backend not working error?

FAQ

What does admin 404 Not Found mean?

The 404 error is an HTTP response code indicating that the server cannot locate the requested file or page.

How can I redirect a 404 error page in Magento 2?

To redirect a 404 error page, navigate to Marketing > Advanced SEO Suite > Redirects, and insert a redirect for any 404 error page. You have the option to redirect visitors to your homepage or, if manually redirecting, to a pertinent category page.

What does a 404 error access log mean?

A 404 error denotes a missing file or resource. Examining the request URI will identify the missing item. Verify your deployment to ensure no files have been unintentionally deleted or removed.