Session verification failed. Please try logging out and back in again

[Sir Osis of Liver]

Had it working correctly in FF for a while with cookies blocked, but now it's erratic.  The gaming thing in the right portal block (82nd/PK) is running a script and dropping a third party cookie from view.light-speed.com.  Take that out and see what happens.

[orpheus82]

Interesting. I just disabled the Ventrilo page and was able to log out and back in 7-8 times and access admin and the tinyportal admin page. Nice to see if this keeps up.

[orpheus82]

I'm doing everything I can to try and bring back the session verification and logging in and out problems and so far, nothing I do seems to create the error we've been plagued with all this time. Looking good!

[Sir Osis of Liver]

Put the Ventrilo page back in and see if the problem returns.

[orpheus82]

Things have been running smoothly ever since. I didn't put up the old vent panel, but I did create a new one a few days ago and re-added it to the site with no ill effects. Thanks so much for helping us troubleshoot this problem!

[davegior]

Can I post here with the same server settings error or do I need a new thread? Don't want to hi Jack this thread.

[Illori]

this thread is marked solved and started by someone else, so please start your own thread.

[airtetdotin]

i am getting same problem on http://forum.airtet.in

[userquote]

Hi, I am running to the exact problem as you did. Cannot post anything to the forum. Cannot login as Admin (error message: Session verification failed. Please try logging out and back in again, and then try again.) Could you share what you did to correct the error? Thanks a lot.

My site address is at www.userquote.com/forum [nofollow]

OK,

The site is playing nice now. I was able to grant you admin privileges.

[MultiformeIngegno]

Same problem. I can't even reset my password (if I type my username in ?action=reminder I get again a "Session verification failed. Please try logging out and back in again".

[MultiformeIngegno]

If can be of any help:
Ubuntu 13.10
PHP 5.5.8
nginx-1.5.9
mysql  Ver 14.14 Distrib 5.5.35, for debian-linux-gnu (x86_64) using readline 6.2

I tried changing all the settings available on repair_settings (database driven sessions, changing cookie name, etc). No luck.

Mine is not a forum really active anymore, so I don't know precisely when this happened. I think it was with some PHP upgrade though. I have no MODs installed.

[dmp1ce]

I don't know if it is the same issue, but turning Database driven sessions to ON helped me login and logout without errors.  Otherwise I could only login after the second attempt and I couldn't logout unless I deleted my cookies.

[sshanky]

OK...here is the way to fix this problem. Found this at maxi-pedia dot com.

THANK YOU TO WHOMEVER POSTED THIS...IT WORKED AND WAS THE ONLY THING I COULD FIND. I ONLY DID STEP A (BOLDED BELOW)

= = = = =

Hello,

I do not know exactly what triggers this message on your end, but the principle is that SMF works with sessions in many ways. It seems to pass them in _GET, _POST, from DATABASE, from COOKIES, etc. If it runs into a situation where your sessiondata in one source is not the same like from the other source, it returns the message. This can happen for example when your hosting provider cleans the sessions temp folder with you logged in. In this case, you would be able to log back in after sessiondata elsewhere expires.

To fix the "Session verification failed. Please try logging out and back in again, and then try again." message:

a) Sessions are stored in your database in the Sessions table (if you have dbase sessions enabled). You can dump this table without problems. In case you decide to manually dump this table, make sure you also delete records from log_online and log_errors. These two tables seem to hold session related data as well (i.e. data related to sessions on your Sessions table).

b) I had some files related to sessions in my temporary folder where I store temp files from my web server. Find out where your server stores temp files and clean that up.
c) Clean up your cookies. Those can store some data related to this.
d) If you are worried about deleting the content of the Sessions table, you can force all sessions to expire by setting the databaseSession_lifetime variable on the Settings table to one.
e) In case you have bad luck, and you can't even log into your admin interface to disable database sessions, you can hack that settings by setting the databaseSession_enable variable to zero in your Settings database table.
f) If nothing helps, you can edit your Security.php file and disable checks related to checking sessions. Find the checkSession() function and uncomment all the stuff that checks for sessions validity.

e) and f) will not fix your problem, but it will at least get you into the system to do more research.

[Arantor]

Steps d, e and especially f are seriously not recommended.