Results 1 to 5 of 5

Hybrid View

  1. #1
    Player
    Baci's Avatar
    Join Date
    Aug 2013
    Posts
    245
    Character
    Baci Asciar
    World
    Zodiark
    Main Class
    Warrior Lv 90
    Friend of mine has that problem atm. Any Solutions other than waiting out there?
    (1)

  2. #2
    Player
    Lolifell's Avatar
    Join Date
    Oct 2013
    Posts
    15
    Character
    Lethe Malheur
    World
    Balmung
    Main Class
    Marauder Lv 80
    Quote Originally Posted by Baci View Post
    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.
    (0)


  3. #3
    Player
    Geist's Avatar
    Join Date
    Mar 2011
    Location
    Limsa Lominsa (1.0) Ul'dah (ARR)
    Posts
    130
    Character
    Geist Geiser
    World
    Ragnarok
    Main Class
    Paladin Lv 70
    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.
    (0)
    Last edited by Geist; 10-03-2017 at 11:41 PM.