Roundcube Community Forum

Release Support => Pending Issues => Topic started by: smart on November 26, 2012, 01:46:59 PM

Title: Session problems
Post by: smart on November 26, 2012, 01:46:59 PM

Hi,
Roundcube is logging me out after a few seconds, session log says this:

Quote

Session authentication failed for XZY; invalid auth cookie sent; timeslot = 1970-01-01 01:00:00

What does this timeslot mean?

Please find below the main.inc.php settings:

Code: [Select]

$rcmail_config['keep_alive'] = 60;
...
$rcmail_config['session_lifetime'] = 10;
...
$rcmail_config['min_keep_alive'] = 60;
Any idea what I'm doing wrong?

Title: Re: Session problems
Post by: IBTB on November 26, 2012, 03:27:14 PM

I'm not qualified to give you a correct answer, but have you set date.timezone in your php.ini file?

Title: Re: Session problems
Post by: smart on November 26, 2012, 06:38:06 PM

Unfortunately yes, that was the last thing I tried.

Title: Re: Session problems
Post by: SKaero on November 26, 2012, 08:08:28 PM

I've seen the same error when force_https/use_https was set incorrectly but that had a current date in the error message. Does the same thing happen on other computers?

Title: Re: Session problems
Post by: smart on November 27, 2012, 06:38:45 AM

Hi,
Thanks for your help!

This is how they are set:

Code: [Select]

$rcmail_config['force_https'] = true;
...
$rcmail_config['use_https'] = false;I use a security certificate, but it's not behind a proxy - so this should be the only correct setting.

And yes, this happens on other computers. :-[

Title: Re: Session problems
Post by: SKaero on November 28, 2012, 03:42:25 AM

Assuming the certificate is setup correctly that shouldn't be a problem and if it was the date in the error message should be current. Can you setup a test account and ftp access for me to test it out?

Title: Re: Session problems
Post by: smart on November 28, 2012, 09:37:11 AM

Hi SKaero,

Thank you so much but I guess the problem was caused by another thing: both locations I tried it from were under a load balance so the IP changed.

Since I deactivated the IP check it seems to work! I'll have an eye on that, but I'm quiet sure that's the reason.

Thanks!