I agree, amazon has to address this.
Also agree that this behaviour dosn’t make sense, but its what is happening to me, in my case, dosn’t matter what character i use, but what server i try to join, in the last beta, i tried to delete and create the charater again on the same server and the problem persisted, maybe we are having a similar, but different, problems.
Idk, could be a problem with the load balancer, but theres no way to dig in deeper on this, we have to rely on the support from now on.
Also, for anyone not willing to pay for a VPN, try CloudFlare WARP, it worked for me.
And that’s why all the solutions they give are mostly wrong.
If it’s an ISP, or an IP problem, you should NEVER be able to login, but that’s not the case.
Same for Firewalls and IPv6.
This just happens too randomly, to be one of the above issues.
This is probably an issue caused by their Server Load Management System they introduced in Patch 1.0 to deal with the queue.
This lines are particularly suspicious:
<2021-10-12 14:48:47.511>: [Info] (AZCore): [GameConnection] GameConnectionWrapper: start REP connection RepAddress = 52.59.207.109, worldId = 5eb2f0f9-e007-4f9e-b8e3-d19673a004d7
<2021-10-12 14:48:47.512>: [Info] (AZCore): [GameConnection] Update state StartREPConnection to new state WaitingForREPConnection
<2021-10-12 14:49:02.845>: [Info] (AZCore): [GameConnection] State(WaitingForREPConnection) is timeout : frames 10, currentTimeoutIntervalCount 1
<2021-10-12 14:49:02.845>: [Info] (AZCore): [GameConnection] Report Error: Reason: 44 BannedUntilEpochMS: 0d
They are using a REP connection instead of a traditional STP connection, and look what I found on the CISCO website regarding the subject:
"• You must configure each segment port; an incorrect configuration can cause forwarding loops in networks. • REP can manage only a single failed port within the segment; multiple port failures within the REP segment causes high loss of network connectivity. • You should configure REP only in networks with redundancy. Configuring REP in a network without redundancy causes loss of network connectivity."
Sounds familiar?
Some servers are NOT configured properly and causing loss of connectivity, please Amazon, fix this mess.
Spoke to customer service again this morning (three week anniversary of being unable to connect) following the new patch. They advised that the issue should be resolved by the patch. It is not. The endless ticket continues…
I’ll redo all the annoying troubleshooting steps again this afternoon. Joy.,
UPDATE: Deleting the two certificates in the EasyAntiCheat certificates folder then validating the game files in Steam seems to have worked after the patch. Hope it works for you too
Such an old post with this problem still persisting. C’mon amazon give us something here, at least admit this is a huge issue and that you will actively work on it.
im tired with this, it happens to me too and not just once. but many times already. ill try many solution and doesnt work for me… what i suppose to do now?!