Forums

i gave it a try and i didn't lose my session too :o

Been facing the issue for over 6 months. Country - Bangladesh

Seems fixed? I hope it won't ever come back.

The authentication code has been updated in the last few days. These updates should now:
- no longer logout users with dynamic IPs (changing once every 24 hours, etc.);
- allow users with hyper-dynamic IPs that change on successive page loads to remain logged in.

I apologise that this issue took so long to be fixed. All of your posts in this thread helped to encourage Crave to change our authentication system, so thank you for your feedback. The intention was to keep the site secure after our terrible hacker experience and I believe the number of users this would impact was underestimated.

If you are still having problems, please:
1. clear your cookies
2. check "Keep me logged in" if you are using your home computer.

If this doesn't work, please give a detailed description of what is happening (how often you are getting logged out) and if this problem is fixed in different browsers. If you can't remain logged in long enough to post, then please join our IRC channel and send me a message.

Thank you all for your patience over the last months and my apologies again for the very long delay.

Holy fucking shit it actually happened

Thanks for fixing this. I had lost all hope for it ever getting better, so it will take a while to for me to truly understand that it really happened, but it's a good thing that you finally made this decision.

Many thanks for solving that issue :)

I haven't had to log in again recently due to the previously mentioned cookie issue. Thank you all!

After 3-4 days of smooth use of the site, I just got logged out out of the blue. Tried logging in by checking "always remember", failed. Logged in without checking it, intentionally logged out and this time successfully logged in "always remember" checked.

When the problem was here, checking "always remember" sometimes caused you to fail to log in. Like this. The fact that it worked at the second time is good, but there's a fair chance that problem is back.

Have you made any changes after the fix? Did you revert back?

Topic Locked.

Please see this thread for the latest updates on this issue.