Computer clock and SL clock causing problems logging in.

"As a temporary workaround, setting your computer clock to Pacific Standard Time should allow you to login."

This doesn't seem to work.

I've just tried three times to login and I'm getting the exact same thing. I'm also noticing that the online numbers are dropping by a thousand each time I've tried. I'm betting there are inworld problems going on at the same time.

I wouldn't be surprised to find out that lots of people are getting kicked out or crashed.

Oh well, I can always go watch a tutorial or do some laundry.

I had to change my clock back by an hour. Most annoying!

I set the time zone to Pacific, didn't work.

I kept my timezone correct and set the time itself to the SLT (Pacific) and it worked.

In any client-server network, all of the client clocks and server clocks must be in sync, or Really Bad Things™ can happen. Various networks have different tolerances for unsynced clocks, but I don't think it's any more than six minutes.

At any rate, it seems the SL server clocks went unsynced or, if the "set your clock to PST" trick works, it sounds like the SL server clocks (at least the login server) reference to UTC got screwed up.

Edit: Given that setting the local time zone didn't work, but setting the clock did, it definitely sounds like a time zone issue on the servers.

Definitely - I tried to relog because I flew into my home sim and it was blank/all ocean and wouldn't load. Can't get back in, obviously. :C

Same here, Bree I set my clock back to PST last weekend, from PDT. And I'm getting the same message. And the time on this post is still in Daylight Savings.

mine worked by putting the clock back to pst and not the timezone

Hey all, I just got inworld! I just kept trying every few minutes and it worked this last time. It just seemed a teensy bit slower is all. Hopefully there won't be any further problems.

Having a consistent time is critical for security purposes. Not only does it relate to expired security certificates, as someone else has pointed out, but it's also used to prevent replay attacks.

Nope it happened a few years ago too...

/me put some more quarters in. Seems fixed now.

Same problem here, but I did set my PC clock to PST and that solved it.

That depends on the protocol; some just don't care, and others depend on synced time.



Heh, in this case the cause was (wait for it) an expired certificate on the login server. That's why changing time to PST worked for a while and then stopped working. After the PST thing stopped working, setting you clock back to an earlier time than that worked until they fixed the cert issue.

It sounds like the SL cock was wrong for a while, but I had that error a few weeks ago. I checked my computer's date and time and it was fine but I still got the error. It wasn't until I checked my computer's date and time more closely that I found it had somehow been changed to the following month - no doubt by me but unintentionally.

snigger