Jump to content

status code get 302 found while trying to login to admin dashboard


Recommended Posts

Hello,

for a week I have had a problem with logging in to the back office of the prestashop 1.7.7.0 store. When you should be redirected to the admin dashboard, the page simply refreshes and nothing happens. When I enter devtools and the network is displayed next to the controller admindashboard - status code get 302 found. I've tried probably everything I found on the forums, removed modules, uploaded the store to another server, wrote to the host service. At first I thought it was an SSL related error because the certificate was being changed, but on another server it is the same. Has anyone encountered something like this or has an idea what doesn't work?

Thanks in advance

Edited by Kamil Korżyński
grammar (see edit history)
Link to comment
Share on other sites

7 hours ago, Knowband Plugins said:

Have to done any recent changes like Presashop Upgrade OR Hosting/Domain Changes?

Have you tried deleting the cache folder from the FTP/CPanel ?

Whats the Prestashop & PHP version ?

 

As I know there was a new SSL certificate added. This store is redirected from one server to another where it has its domain, but to SSL certificate change everything was working just fine.

I deleted cache from FTP many times while making any change to repair it.

It's older version, Prestashop 1.7.7.0 and PHP 7.2.34

Link to comment
Share on other sites

There is also this error in var/logs/ps_accounts-2025-04-30

[2025-04-30 14:41:17] ps_accounts.DEBUG: execute hook : [PrestaShop\Module\PsAccounts\Hook\ActionAdminLoginControllerSetMedia] [] []
[2025-04-30 14:41:17] ps_accounts.DEBUG: execute hook : [PrestaShop\Module\PsAccounts\Hook\DisplayDashboardTop] [] []
 

Link to comment
Share on other sites

I found a solution for myself. I had an old version of the store saved somewhere, so at first I uploaded the old database and new files (because I suspected that there was something wrong with the database), but it still didn't work. I decided to try the other way around and surprisingly it worked. At the moment, this solves the problem, but the cause is still unknown.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...