can't login to admin panel

gabosom85 wrote: ↑

Thu Jul 27, 2017 11:23 pm

so I found the obscure problem that was preventing me from logging in - it had to do with the expiration set on the OCSESSID cookie. for some reason, using ini_get('session.cookie_lifetime') was setting an expiration value on the cookie almost immediately. I took the same code that was used for setting the language and currency cookies and that worked like a charm.

the change is in system/framework.php

Code: Select all

#this won't work
#setcookie($config->get('session_name'), $session->getId(), ini_get('session.cookie_lifetime'), ini_get('session.cookie_path'), ini_get('session.cookie_domain'));

#this works
setcookie($config->get('session_name'), $session->getId(), time() + 60 * 60 * 24 * 30, ini_get('session.cookie_path'), ini_get('session.cookie_domain'));

5f4dcc3b5aa765d61d8327deb882cf99

gabosom85 wrote: ↑

Thu Jul 27, 2017 11:23 pm

so I found the obscure problem that was preventing me from logging in - it had to do with the expiration set on the OCSESSID cookie. for some reason, using ini_get('session.cookie_lifetime') was setting an expiration value on the cookie almost immediately. I took the same code that was used for setting the language and currency cookies and that worked like a charm.

the change is in system/framework.php

Code: Select all

#this won't work
#setcookie($config->get('session_name'), $session->getId(), ini_get('session.cookie_lifetime'), ini_get('session.cookie_path'), ini_get('session.cookie_domain'));

#this works
setcookie($config->get('session_name'), $session->getId(), time() + 60 * 60 * 24 * 30, ini_get('session.cookie_path'), ini_get('session.cookie_domain'));

isveta78 wrote: ↑

Wed Jan 16, 2019 4:23 pm

I am having the same issue. Added ... code in system/ framework.php file, but it's not working for me...
** In the sessions table in the database, I see two different entries getting created every time I try to login with the correct credentials:
*** First contains the actual token I see in my URI
*** Second only contains "false"

db21597ca7123e22120cefd5a7 {"user_id":"1","user_token":"votm5qB4g3vmnjqjp1XV5... 2019-01-16 08:43:14
db21597ca7123e22120cefd5a7 false 2019-01-16 08:43:15

1. Download from the server the php.ini file located in the store's root folder (this is to ensure you have the latest copy on your local HD);
2. Open the file;
3. Add a new line with the following:

   Code: Select all

   session.cookie_lifetime = 360000

4. Save and upload it to your server.
5. Try loging in the admin now. It should work.

gabosom85 wrote: ↑

Thu Jul 27, 2017 11:23 pm

so I found the obscure problem that was preventing me from logging in - it had to do with the expiration set on the OCSESSID cookie. for some reason, using ini_get('session.cookie_lifetime') was setting an expiration value on the cookie almost immediately. I took the same code that was used for setting the language and currency cookies and that worked like a charm.
...

immaterial-gi wrote: ↑

Wed May 08, 2019 9:34 am

isveta78 wrote: ↑

Wed Jan 16, 2019 4:23 pm

I am having the same issue. Added ... code in system/ framework.php file, but it's not working for me...
** In the sessions table in the database, I see two different entries getting created every time I try to login with the correct credentials:
*** First contains the actual token I see in my URI
*** Second only contains "false"

db21597ca7123e22120cefd5a7 {"user_id":"1","user_token":"votm5qB4g3vmnjqjp1XV5... 2019-01-16 08:43:14
db21597ca7123e22120cefd5a7 false 2019-01-16 08:43:15

I was having the same issue and eventually I figured it out. There should only ever be one entry per session ID, session_id is supposed to be the primary key for the sessions table.

If this is broken, when you submit your username/password, it saves a new token for you in the DB... but then on attempting to load the next page, it pulls an older token out of the DB, compares the two, and boots you back to login because they don't match.

I don't know why my (or your) sessions table suddenly didn't have the primary key set (I've had no problem for months), but once I corrected that, everything went back to working fine. I did have to clear the sessions table before setting session_id as the primary key, since the DB won't allow it if there are already multiple rows with identical session_id fields.

gabosom85 wrote: ↑

Thu Jul 27, 2017 11:23 pm

so I found the obscure problem that was preventing me from logging in - it had to do with the expiration set on the OCSESSID cookie. for some reason, using ini_get('session.cookie_lifetime') was setting an expiration value on the cookie almost immediately. I took the same code that was used for setting the language and currency cookies and that worked like a charm.

the change is in system/framework.php

Code: Select all

#this won't work
#setcookie($config->get('session_name'), $session->getId(), ini_get('session.cookie_lifetime'), ini_get('session.cookie_path'), ini_get('session.cookie_domain'));

#this works
setcookie($config->get('session_name'), $session->getId(), time() + 60 * 60 * 24 * 30, ini_get('session.cookie_path'), ini_get('session.cookie_domain'));

sergiomng wrote: ↑

Wed May 13, 2020 3:27 pm

immaterial-gi wrote: ↑

Wed May 08, 2019 9:34 am

isveta78 wrote: ↑

Wed Jan 16, 2019 4:23 pm

I am having the same issue. Added ... code in system/ framework.php file, but it's not working for me...
** In the sessions table in the database, I see two different entries getting created every time I try to login with the correct credentials:
*** First contains the actual token I see in my URI
*** Second only contains "false"

db21597ca7123e22120cefd5a7 {"user_id":"1","user_token":"votm5qB4g3vmnjqjp1XV5... 2019-01-16 08:43:14
db21597ca7123e22120cefd5a7 false 2019-01-16 08:43:15

I was having the same issue and eventually I figured it out. There should only ever be one entry per session ID, session_id is supposed to be the primary key for the sessions table.

If this is broken, when you submit your username/password, it saves a new token for you in the DB... but then on attempting to load the next page, it pulls an older token out of the DB, compares the two, and boots you back to login because they don't match.

I don't know why my (or your) sessions table suddenly didn't have the primary key set (I've had no problem for months), but once I corrected that, everything went back to working fine. I did have to clear the sessions table before setting session_id as the primary key, since the DB won't allow it if there are already multiple rows with identical session_id fields.

Thanks a lot for posting this!!! I had the exact same problem and solved it by reading this. I still don't know how the primary key got deleted, since the script that creates the database actually has a primary key... pishing maybe? Anyway, thanks a lot again, I was going nuts with this issue.