172 replies to this topic

[Kagemonshi]

Damn. This works. Thanks.

[Appalachia]

Working for me as well. Cant find a match, oh well.

[Don Pellegrino]

Enough of us are using that trick, I was able to find a match in 10 seconds!

[Bud Crue]

pwnfred, on 19 June 2022 - 08:36 AM, said:

TLS Cert expired ... LOL
Set system time back to Jun 16th BAM login successful.

But noone else online:

TLS certificate updating and housekeeping is a ***** for unskilled team/management
Are we surprised that PGI found that trap...

Kagemonshi, on 19 June 2022 - 09:04 AM, said:

Damn. This works. Thanks.

Would one of you kind-hearted computer literate folks give a "how to" on how to do this? Is this like a system restore, type thing or something else?

[XxXVedi SYSTEMFEIND ViciXxX]

Same..................

[Kagemonshi]

Bud Crue, on 19 June 2022 - 09:17 AM, said:

Would one of you kind-hearted computer literate folks give a "how to" on how to do this? Is this like a system restore, type thing or something else?

Just set your date and time manually on your PC back to June 16th. Also disable "Set time automatically"

[Don Pellegrino]

1. Press Windows key
2. Type "Settings" and open it
3. Go to "Time & Language"
4. Turn off "Set time automatically"
5. Click on "Change" (next to "Set the date and time manually")
6. Set the date to June 17
7. Done! it will let you login

Just don't forget to put it back on "Set time automatically" after PGI has fixed the issue on their end

Edited by Don Pellegrino, 19 June 2022 - 09:23 AM.

[Faol]

@Bud Crue, right-click on the time displayed at the lower right bottom of your desktop, chose change time/date, uncheck the automatic updating of time/date, then set a new date: 16th of june 2022.

Edited by Faol, 19 June 2022 - 09:24 AM.

[Bud Crue]

Don Pellegrino, on 19 June 2022 - 09:22 AM, said:

1. Press Windows key
2. Type "Settings" and open it
3. Go to "Time & Language"
4. Turn off "Set time automatically"
5. Click on "Change" (next to "Set the date and time manually")
6. Set the date to June 17
7. Done! it will let you login

Just don't forget to put it back on "Set time automatically" after PGI has fixed the issue on their end

LOL. Worked like a charm. Thanks!

[pwnfred]

Duke Falcon, on 19 June 2022 - 08:37 AM, said:

You may need to wait as the error created somehow by the developers. Error 13 is an installation\uninstallation error connected to DLLs and mostly registry entires try to find and run those files but can not. Someone tinkered with core files and made some bug. Do not stand on one leg 'till they fix it as it may take even hours if not days...

No srry due the TLS handshake fails with an error by which the client states SSL alert and drops the connection.
And this tells that the cleint does not like the server cert === It's expired

[MegaBopper]

Greetings Mechwarriors,

For your information I have submitted the following request to what I hope is the correct destination at PGI:

MegaBopper said:

In view of the current serious issue regarding the availability of Mechwarrior Online during the weekend of June 18-20, 2022, I respectfully request that PGI would please extend the expiration period for redemption of earned awards in the current events for all players by at least five days following the return of the system to active availability.

Because of the high likelihood that there are many players with awards that they intended to redeem during this weekend I believe that this is the appropriate and right thing to do.

If you feel that same you may wish to act on it according to your own considerations on the matter.

Looking forward to a swift resolution,

[Eramen]

Don Pellegrino, on 19 June 2022 - 09:22 AM, said:

1. Press Windows key
2. Type "Settings" and open it
3. Go to "Time & Language"
4. Turn off "Set time automatically"
5. Click on "Change" (next to "Set the date and time manually")
6. Set the date to June 17
7. Done! it will let you login

Just don't forget to put it back on "Set time automatically" after PGI has fixed the issue on their end

Queuing for a game. Thanks!

[Warbrynger]

6-19-2022 @ 1:00pm

VERIFIED - if you change your local computer date back to 6-17-2022, you are able to log in and play without the Error 13.

as some have surmised, the issue is most likely a certificate that expired on 6-18-2022. The local game client has a fail-over of Error 13 when it cannot properly connect to the server for login.

if you change the date - you can log in and play. on my third game now.

[Vanguardian C64]

Ok, be forewarned that your firewall or anti-virus may be irritated with this change. You also may encounter problems with other programs that depend upon the internet. No permanent problems though, as soon as you change to the correct date everything will be fine.

Windows 10, (And probably all versions)
Desktop- click on the time in the lower right corner of the screen.
When the calendar pops up click on date and time settings.
Turn off "Set time automatically"
Below "Set the date and time automatically" click Change.
On the drop down for the date select 16.

Later, to put things back in order, do the same steps to get there and
Turn ON "Set time automatically"
and under "Synchronize your Clock" click Sync Now.

[Herod]

Workaround will get you in, but seems to be some awful lagging or rubber banding going on.

[pwnfred]

Herod, on 19 June 2022 - 09:52 AM, said:

Workaround will get you in, but seems to be some awful lagging or rubber banding going on.

Yep

The netcode relies on client side time information.
With custom times on all client the server goes like
"HE is there a time A but THAT GUY states its time B"
MAD MAD MAD MAD I go

[Don Pellegrino]

The game is working just fine with the workaround and lag free for my whole group. If you're experiencing lag it's most likely due to something else.

Quote

HE is there a time A but THAT GUY states its time B

The game won't rely on your local time for this, don't worry.

Edited by Don Pellegrino, 19 June 2022 - 10:05 AM.

[Bud Crue]

Herod, on 19 June 2022 - 09:52 AM, said:

Workaround will get you in, but seems to be some awful lagging or rubber banding going on.

Played 3. Wait times not a big deal, but the lag was a fun killer.

[Nesutizale]

The date you have to set the clock back to... wasn't that the time where Windows made a new update?
I know there was a new windows update lately but don't remember the date.

[R_Wolfhound]

Sunday... and the error is still there.