Thread

So running with Chrome on OSX - have a heap of sites with accesible CP - no dramas except for one. The related post mentioned something about the servers timezone - strange.

So after stuffing around with EE server timezone to no effect, I looked closely at the dev server and the live server via PHPinfo.

Note: The dev server is on the same server set as the rest of our “working” installs and the “live” server is sitting on another host altogether which is the only major point of difference. They assure us the timezone stuff is kosher on the server.

The only thing different between them:
location dev +10 // live is +9.5
“Olson” Timezone Database Version dev = 2010.9 // Live = 0.system
Default timezone dev = Australia/Melbourne // Live = Australia/Adelaide
Installed from dev -> live via DB Import & Bootsrap

Running EE 2.4, everything works on every other browser

Really need a some hands on loving on this one.
Has anyone identified why Chrome stumbles on this apparent Time Zone issue ?

Cheif, your tale is setting off all kinds of intuitive ideas of what code may be in EE that is involved in this—and other issues that turn up with cp logins. I’m probably wrong about all of them, but the experience is interesting.

Does it help if you set your workstation to the same half-hour-off timezone as the problem server, so that its time to the minute is the same?

It seems that it might help get this to work, and if so, also give a clue to someone responsible. Or otherwise, help discover it’s another problem with that server.

Regards,
Clive

Hello Cheif,

I am sorry to hear you are running into this snag.

What is the actual issue you are dealing with in Chrome? Are you unable to see the Control Panel login?

You mention a related post. Can you point me to that one?

So this issue only shows up when using Chrome and only on this one site?

I will be on the lookout for your response.

Regards,

The related issue was here: http://ellislab.com/forums/viewthread/205808/

After emailing the host they confirmed the time was spot on. 24 hours later, they had actually looked at the server time and found it was out by microseconds.

Chrome loads the CP login screen and after submitting credentials reloads the page. Put in bogus credentials and it alerts you per normal.

The burning question is now - Just what is happening that is microseconds time dependant enough to trip up a very robust system, a system that all otehr browsers have no issue with ?

Does it happen if you test from a different computer, still using Chrome?  And if you look at the live headers (how to) is it setting the cookie and if so- what’s the cookie setting?

And why it affects only Chrome?  That, I can’t say.  If it were IE, I’d be less surprised.  Heh.