Can't log in to Magento Admin

Question

I'm having troubles logging into Magento's admin panel on one of our staging sites (it works 100% on our webdev servers and was working just fine not too long ago on the staging server as well).

I've done some research, and most people suggest that it's got to do with running Magento on a localhost and browsers not saving cookies for domains with no dots in the domain name. The problem with that, however is that we're running it from http://staging.sitename... etc.

Another few things that were suggested are where someone changed the default name for accessing the admin in the config, but we haven't changed it.

Does anyone have any ideas that might help?

Thanks for taking the time to help me out!

Kind Regards,
Rémy

[After installation, I solve it by clearing cache](http://www.magentocommerce.com/wiki/how_to_fix_login_for_admin_on_local_install) — Yeo, May 13 '15 at 12:01
Check here, same problem you are facing: http://magento.stackexchange.com/questions/85958/magento-admin-login-issue — Jóni, Oct 12 '15 at 12:02

score 40 · Accepted Answer · answered Feb 01 '10 at 16:08

40

I managed to fix it! I found this solution here: http://blog.chapagain.com.np/magento-admin-login-problem/.

I wanted to know why that fixed it though and var_dumped the items I commented out and realized that the cookie domain was being set to just '/' and we have magento set up under '/shop/'. So I went to the configuration section (having managed to log in after commenting out the 3 lines mentioned in the article), changed the Cookie Domain and Cookie Path to be blank and saved. I then uncommented those lines and tried again and all's working well!

answered Feb 01 '10 at 16:08

user223731

689
1
7
10

2

I think it's not good to change the code just to be able to login. as you can see you are commenting either the domain, secure or httponly options. you can easily just change that on your database: update core_config_data set value = 1 where path like '%cookie_http%'; update core_config_data set value = NULL where path like '%web/cookie/cookie_domain%'; update core_config_data set value = 0 where path like '%web/secure/use_in_adminhtml%'; – useless Jul 11 '15 at 19:25

score 18 · Answer 2 · answered Nov 19 '12 at 06:00

18

In new Magento Installation, do the following ->

Open the file

app/code/core/Mage/Core/Model/Session/Abstract/Varien.php.

and change the code at line 87 to this ->

    $cookieParams = array(
        'lifetime' => $cookie->getLifetime(),
        'path'     => $cookie->getPath(),
      //  'domain'   => $cookie->getConfigDomain(),
      //  'secure'   => $cookie->isSecure(),
      //  'httponly' => $cookie->getHttponly()
    );

answered Nov 19 '12 at 06:00

Shashank Agarwal

712
8
14

Can you update the answer for Magento versions > 1.3? https://wiki.magento.com/display/m1wiki/Cannot+log+in+to+the+Magento+1.x+Admin+Panel+on+Local+Installation – tjons Nov 25 '15 at 21:35
I'd recommend creating a custom module and overriding the function in there, don't directly edit core code – Nov 03 '16 at 12:44

score 15 · Answer 3 · answered Mar 11 '13 at 05:19

15

I have also encountered this issue. This is what I did : In core_config_data, delete any rows where path = web/cookie/cookie_domain

answered Mar 11 '13 at 05:19

Nithin

151
1
2

1

I didn't delete it just updated for my domain, worked a charm. – jzahedieh Apr 15 '14 at 08:52
I didn't have an entry, but when I added one it started working, I think its because I'm hosting it on a VM on port 8080 instead of port 80. – Ray Sep 29 '14 at 19:20

score 6 · Answer 4 · answered Apr 26 '14 at 08:12

6

Just clear cookies and cache in web browser. It works for me perfectly.

answered Apr 26 '14 at 08:12

Marcin Gucia

63
1
3

score 2 · Answer 5 · answered Jul 02 '12 at 02:24

2

I have also encountered this issue. This is what I did : In core_config_data, delete any rows where path = web/cookie/cookie_domain

answered Jul 02 '12 at 02:24

phagento

410
4
13

score 2 · Answer 6 · edited May 23 '17 at 12:03

2

Having the specific error would help. A couple shots in the dark -

It's worth checking your rewrites. I've had issues moving from server to server where one of them doesn't have the rewrite setup correctly. if servername.com/index.php/admin works, but servername.com/admin doesn't, then you have a rewrite issue.

It could conceivably also be that the base_url is not configured for the right server. Did you change it when you moved the database over? See my answer at this post for details.

edited May 23 '17 at 12:03

Community

1
1

answered Feb 01 '10 at 14:43

Laizer

5,932
7
46
73

1

Thanks for your response! The problem is that there is no real error aside from the fact that it's not letting me log in. It's definitely not the base_url as I've checked in the magento_core_config_data table and it's got the staging link in there. It's also not the rewrite issue because I can see the page when I go to /admin without index.php at the end (I did try anyway just for good measure). It just ends up on the login page every time I click login. The only difference occurs when I deliberately put in the wrong login info, in which case it tells me I got the wrong username or password. – user223731 Feb 01 '10 at 14:56

score 2 · Answer 7 · edited Apr 13 '17 at 12:54

Hi I had the same problem and I solved it by deleting all files in /var/session . I think it's because too many session in Magento!

and for security, I changed 'Use HTTP only' to 'No' in 'Session Cookies Management' of the 'Web' settings after I can loggin again..

I found this solution on the internet:https://magento.stackexchange.com/questions/26071/magento-1-9-can-t-login-to-admin-panel

score 1 · Answer 8 · edited Jan 11 '13 at 19:28

Our site was running fine for months, then today no one could log into admin, nor could our users log into their frontend accounts. We run on a linux server.

Solution: the /magento/var/session directory was full of sess_* session files, so many in fact that attempting to execute rm * failed. After a tedious whacking of session files piecemeal (rm sess_1*, rm sess_2*, . . . rm sess_a*, rm sess_b*, . . . rm sess_v*) all of a sudden I could log into Magento again. Actually, I was able to log in after whacking just a few batches.

Theory: when the session directory has too many files, Magento may not be able to create new session files in a timely fashion, or maybe not at all.

score 1 · Answer 9 · answered Sep 09 '13 at 18:54

1

I can´t access to backend!

(Solution for me):

app/etc/local.xml line 55

    <session_save><![CDATA[files]]></session_save>

replace

    <session_save><![CDATA[db]]></session_save>

answered Sep 09 '13 at 18:54

Jean Paul CP

253
2
10

score 1 · Answer 10 · answered May 27 '14 at 02:07

1

If you use sample data:

Change: app/etc/local.xml line 55

<session_save><![CDATA[files]]></session_save>

replace

<session_save><![CDATA[db]]></session_save>

Then: Clear browser cache

answered May 27 '14 at 02:07

Z. Rahman Raju

829
7
5

score 1 · Answer 11 · answered Jun 24 '14 at 18:13

1

We had the same issue and it was due to the server hard drive running out of space. Magento couldn't create a new session and therefore wouldn't log us in. Freed up the space and the issue was solved.

answered Jun 24 '14 at 18:13

NateFriedman

530
4
9

score 1 · Answer 12 · answered Feb 06 '16 at 18:01

1

I have found a new simple way to solve this issue. I have spent hours and at the end I have, maybe for desperation, this step: Request the Administration password.

So, go to the admin login page and click on the forgot password link.

Change the password, and now you can login again!

Regards

answered Feb 06 '16 at 18:01

Michelangelo

1,398
2
14
37

Surprisingly, that was the right thing to do in my case too ; thanks for the tip! – nicolallias Oct 18 '17 at 10:41

score 1 · Answer 13 · edited Jul 12 '16 at 05:09

1

Need to update 3 things in the core_config_data table for following paths:

web/secure/base_url
web/unsecure/base_url
web/cookie/cookie_domain

use commands like

UPDATE 'core_config_data' SET 'value'="localhost.com" WHERE path="web/cookie/cookie_domain"

and do not forget to clear cache and browser cookies.

edited Jul 12 '16 at 05:09

Paul Roub

36,322
27
84
93

answered Jul 12 '16 at 05:06

th3pirat3

559
8
19

score 1 · Answer 14 · answered Aug 20 '11 at 23:08

1

I solved just by cache clearing (execute php mage clear-cache from your Magento base directory

answered Aug 20 '11 at 23:08

Dmitri Sologoubenko

2,909
1
23
27

score 0 · Answer 15 · edited Jul 12 '16 at 05:21

0

I had the same issue, and it was all with the localhost.

First i changed web/unsecure/base_url and web/secure/base_url. These both config values were having localhost and i replaced it by 127.0.0.1 . Still it was not working until i deleted all contents of two folders var/session/ and var/cache/.

Now it is working fine.

edited Jul 12 '16 at 05:21

Manashvi Birla

2,837
3
14
28

answered Feb 06 '14 at 05:44

Altaf Hussain

5,166
4
30
47

score 0 · Answer 16 · answered Aug 12 '14 at 21:34

I have been to the bottom of page 2 of gogole search results to try and solve this problem. I did everything I could find that was suggested. My friend then suggested this command line tool n98-magerun. Running php n98-magerun.phar cache:flush solved it. I could then log in. There's loads of commands though, so if that doesn't work, maybe another will.

score 0 · Answer 17 · answered Jan 06 '16 at 08:57

0

After applying so many solutions and answers, this one worked at last.

Comment the Line 108~

call_user_func_array(’session_set_cookie_params’, $cookieParams);

in file app/code/core/Mage/Core/Model/Session/Abstract/Varien.php

answered Jan 06 '16 at 08:57

Mirza Vu

1,532
20
30

score 0 · Answer 18 · answered Sep 21 '16 at 13:51

0

For what is is worth, check that your password field in admin_user is at least 100 characters.

If it is 40, changing the password will not work.

answered Sep 21 '16 at 13:51

tread

10,133
17
95
170

score 0 · Answer 19 · answered May 16 '17 at 15:28

0

I did a simple method. I went to phpMyAdmin then used a new password with MD5 hash. Then successfully logged in with that password

answered May 16 '17 at 15:28

mofidul

119
3
11

score 0 · Answer 20 · answered Apr 29 '19 at 09:29

0

In my case session folder was missing under var folder. I just created var/session folder and set permission to 777, cleared cache and done.

You should check sysytem.log for this.

answered Apr 29 '19 at 09:29

Ashwani Panwar

3,819
3
46
66

score 0 · Answer 21 · answered Jun 10 '20 at 05:32

go to Varien.php app\code\core\Mage\Core\Model\Session\Abstract\Varien.php cleanup the files of var folder and make the mentioned changes:

        //session cookie params
        $cookieParams = array(
            'lifetime' => $cookie->getLifetime(),
            'path'     => $cookie->getPath()
            // 'domain'   => $cookie->getConfigDomain(),
            // 'secure'   => $cookie->isSecure(),
            // 'httponly' => $cookie->getHttponly()
        );

score -1 · Answer 22 · answered Jun 06 '19 at 16:29

-1

Clearing the application storage from Chrome's DevTools fixed this issue for me.

answered Jun 06 '19 at 16:29

GarryOne

1,430
17
21

score -2 · Answer 23 · edited Jan 23 '14 at 08:34

After doing all of that, And leaving all aforementioned solutions in place, still none of that worked for me. I run Win 7 + XAMPP and Magento Community magento-1.7.0.2

I could see the front-end, but no go on the login to the admin panel at all. All attempts were met with Invalid Username or Password, So I started messing with the Model files to debug, and finally changed

\app\code\core\Mage\Admin\Model\User.php line 340

From this :

if ($sensitive && $this->getId() && Mage::helper('core')->validateHash($password, $this->getPassword())) {

To this :

if ($sensitive && $this->getId() || Mage::helper('core')->validateHash($password, $this->getPassword())) {

Since it's a dev box, it will remain optional to validate password hashes I suppose

NOTE: Do not do this on a live environment, passwords will pass every time regardless to whether they are correct or not as long as your username is correct.

Essentially this code does the following if(username = correct or password = correct){LOG IN} - This means if it passes the username it will log them in.

Can't log in to Magento Admin

23 Answers23

Linked

Related