A System Error has occurred-2146697211 - HTTPS System Error

[Vireon]

Goodmorning Im currently receiving these error was playing fine at trial enjoyed the game and upgrade (bought the game) digital version after that immediately i started receiving on the launcher "A System Error Has Occured: -2146697208" then i evolved to 2146697211

ive tried to running in administrator mode clearing cache at Iexplorer and at lan settings autodetect etc what ever i could scrap out from the forums for help but still couldn't find a solution

plus iam trying to contact support at http://support.eu.square-enix.com/main.php?id=5383&la=2
but i cant connect there.

[Vireon]

ok after 9 hours or so it seems its fixed now (no idea how ) and its downloading a huge patch 8gb and more.

[Baci]

Friend of mine has that problem atm. Any Solutions other than waiting out there?

[Lolifell]

Friend of mine has that problem atm. Any Solutions other than waiting out there?

Having the same exact issue right now. Can't open the launcher, it gives me the same exact error. No idea on what to do.

[Geist]

EU player here - on Ragnarok, Chaos datacenter (I was previously on Excalibur, NA).

This has been an episodic occurrence for me, too. I'm under the impression that certain routes to the lobby server and on occasion the forums aren't working reliably at all times - most likely because of nodes experiencing problems down the pipeline (somewhere in between your point of origin and SE) and failing and/or operating erratically under duress.

This seems to be corroborated by the fact that you could get the client to work as expected and access the lobby by using a different connection method:

- tethering to your smartphone;
- tunneling through a VPN service.

The first one is probably the most accessible and painless temporary solution for average players, but in both instances, please make sure that there's some degree of encryption turned on. Then get ready to switch back to your "regular" connection once you're at character select, and everything should work as expected (the issue isn't affecting the datacenters).

So, it's most certainly a network/bad routing issue, rather than a client configuration/software-side problem. Hopefully the routes will stabilize in time for the release of patch 4.1.