Whoops! Your session has expired.

[RoboPhung]

Ok so I believe I've pinpointed the exact cause of the problem.

So basically, if i am logged in as a customer, and at any point during my session while building my shopping cart, if I go idle and I am timed out...once I log back in, everything appears fine and I can continue to shop, but the moment I attempt to check out, and hit the final button to "confirm order" I get thrown into a session timeout loop.

So somehow there is some kind of mismatch or disconnect between client session and server session in this particular situation right when submitting payment information for processing.

This also explains why I'm hitting an unusual number of customers complaining to me about this issue, since my store format is wholesale and customers can potentially load their shopping cart up with numerous products, they can take up to an hour or more to build and finalize their shopping cart. There is a high probability that they might go afk at some point during their shopping and come back to find themselves logged out, but when they log back in to continue shopping and checkout, the session timeout loop occurs.

The problem seems to be resolved only when closing the web browser entirely and reopening it, logging in, and attempting checkout again.

I tested this both on IE9 and chrome and the same thing occurs.

I am not sure if this issue exists in vanilla 1.3.9h without any additional modules added in, as I have not had the time to run further tests into that much detail. I'll roll back an earlier backup of my store into a test subdomain and try to see if this issue still exists, as soon as I can but Dr. Byte, if you have a test server all set up already, and handy to test this scenario out, perhaps you can help me run a quick test on this scenario at your convenience? Thank you so much for all the assistance you provide on a daily basis to everyone.

[RoboPhung]

So my webhost changed some security settings on their end (the details of which I am not sure of), and that appears to have resolved my session timeout issues in my specific scenario. Everything's working great now. Problem solved!

[DrByte]

So my webhost changed some security settings on their end (the details of which I am not sure of), and that appears to have resolved my session timeout issues in my specific scenario. Everything's working great now. Problem solved!

Any chance you can drag those details out of them? It might be quite helpful for others in the future.

[RoboPhung]

I had spoken too soon about what I thought was the solution...as the problem crept up again, and I was able to trigger it.

I messed around in my admin and changed "check ssl session id" to true (that being the only change) and so far it also seems to be holding up, and passing all my attempts to trigger the timeouts...but I'll need to test more comprehensively before preemptively suggesting that it's a working solution.

[DrByte]

It would be rare for that to be the "fix".

[dochsa]

Hi All I am suddenly having the same issue. Evenytime I click on Checkout, the session seems to time out? Any help is appreciated. This has happened over night and Im unsure as to what has happened.

Site: www.assceneon.com/catalog

Donovan

[GerryTheMole]

I have had this issue with 1.3.9h and the Cardsave module from Ceon. I found the slamming code and it is actually set to THREE attempts not SIX. (I have checked the 1.5.1 code and the same applies). BUT!! and like me it's a big but! If you encounter 3d (secured by visa or whatever you know it as) the attempt count halves. You now have 1.5 attempts so you make 1 mistake - and people do - and when you try the 3d secure second time you have already used you full quota. By upping the attempt count to SIX I then find I get a genuine 3 attempts with 3d but, obviously, six without 3d.