Thread

Hi ejaedesign,

Pascal and I uncovered the problem. First, your server offset (under Localization) is oddly set to 138, so you probably want to check on that. Ideally, you want to be able to have that set to 0 and keep your server time set correctly.

What Pascal discovered was that if we set $config[‘cp_session_ttl’] in your config.php file to a high number (so that the session doesn’t expire for a long time), we could login to all browsers just fine. So it appears that Webkit-based browsers (this login failure behavior exhibits in both Chrome and Safari) were considering your session already expired.

I’d recommend checking with your server administrator to see if your server time is set correctly. Once it is, do you still experience issues with logging in with Chrome/Safari?

Thanks Kevin.

Much appreciated—the server time had to be set to 138 as we had a tough time making correct time stamp to each entry for the entry_date value.

We can now login to Chrome, but we’re still seeing the issue on a fresh install on different domains (w/o any localization changes).

We could however, login if the password was reset on Chrome/Safari after resetting the localization time as well. Is there a reason why that may be the case?

We can now login to Chrome, but we’re still seeing the issue on a fresh install on different domains (w/o any localization changes).

I would imagine this is because the problem is related to your server’s clock. It’s likely not set correctly, so the issue is going to present itself in all installs of EE where the $config[‘cp_session_ttl’] isn’t set to expire in the far future. Check with your system admin to correct the server’s clock.

We could however, login if the password was reset on Chrome/Safari after resetting the localization time as well. Is there a reason why that may be the case?

Hmm… nothing that comes to mind. When you say “resetting the localization time”, what are you doing exactly?

Thanks very much Kevin.

I’ll look into resetting the server time now, and see if that fixes all Chrome login issue. Much appreciated!

Hi Jae,

We’ll leave this thread open until you’ve had chance to test this out. Just let us know when you’ve found anything out here, thanks.

Thanks to Kevin & Pascal too as I don’t think I would have ever thought of that at all 😉

Thanks,

Mark

Hi ejaedesign,

Were you able to come to a solution by ensuring your server’s time was set correctly? Let us know if we can be of any more help!

Hi Kevin,

Yes! We’re all set after server time has been reset. We can mark this thread “happily resolved”.

Hi ejaedesign,

Happily resolved it is! If you need assistance in the future, please let us know in a new thread.

Thanks!