Massively writers trying to play Lord of the Rings Online this Saturday morning stumbled into a mess that's apparently been going on most of the day; upon trying to log into the game, the following error appears: "The SSL certificate appears to be expired. Please ensure your system clock is set to the correct time and try again. [ERROR 80001]" Investigating the LotRO forums has uncovered an official thread from CM Tarrant resassuring players that Turbine's NetOps team is looking into it.
Meanwhile, players have already solved the issue. If you want to get into the game, just set your computer's clock back to January 1st. The complication there is that daily quests might then be tweaked out, and so further recommendations state you should set your computer's date and time to the correct values at the character select screen. Essentially, set the clock back to log in, and then reset once you're past the loader. Turbine assures this issue will be resolved soon, and we can't imagine this seemingly minor error will continue much longer.
Update: And resolved it was, at around 2pm ET. Sapience wants everyone to be sure to set their computers for the correct time if you used that as a cheap workaround. That should ensure the SSL error doesn't show up for you.
Reader Comments (5)
Posted: Jan 3rd 2009 1:40PM KwisatzHaderach said
great, how am i going to get my crack fix now?
Posted: Jan 3rd 2009 1:39PM Softserve said
Looks like it's fixed: http://forums.lotro.com/showthread.php?&postid=3263449#post3263449
I never experienced the problem, guess I'm lucky.
I never experienced the problem, guess I'm lucky.
Posted: Jan 3rd 2009 5:13PM (Unverified) said
i love it when big company's make these stupid errors, I always imagine some dude at the office going, 'OMG, If the boss sees this im in it deep' then 30 seconds later the same dude is staring at a ringing phone with a sudden loss of bladder control.... ooo rambling am i...
either way, minor inconvenience, more funny than anything else, i lol'd
either way, minor inconvenience, more funny than anything else, i lol'd
Posted: Jan 3rd 2009 5:56PM (Unverified) said
Make sure the BIOS time & date is set correctly on your PC. Worked for me didn't need to screw around with the Windows time & date settings.







