Unable to establish connection with the server

Try ExitLag using the 3 day trial and see if it works for you.

1 Like

Same error here but sometime i can join game if i spam play button.

1 Like

Yes, me too.

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.

3 Likes

same here

1 Like

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 :slight_smile:

Unfortunately this also did not fix it for me. I can still only play while hotspot

I wish this worked for me friend, as it did not. I only had one file in my EasyAntiCheat that was a certificate.

Damn TEKKEN don’t do all of their work for them.
Amazon why is TEKKEN serving you guys up like this? No answers?

Delete this two cert files didn’t help.
Issue still persist.

bumppp

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.

I think they really refuse to. And ya know what, it might as well be the reality because they’re not on here correcting anyone either.

Yup, really sad that the issue still persists.

Tried all the suggestions here, nothing has worked.

Playing on mobile internet as a work around is getting tiresome. Will probably take a break and keep following this thread. Hope they get to it soon.

Trying to keep this bumped up, preying Amazon will stop ignoring it.

bump.

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?!

like really not a single response from amazon to let ppl know what countries can play the game what is not

ty bro helped

Hi all,

Small update. So I went to start the game from steam today (after they turned trading etc back on), and a small box popped up, EULA, which was blank. Just clicked on Agree, game started up and I was able to login like normal! No error. First time I’ve seen this pop up I think.

I played for an hour, then tried to test the login again. Back to the same error, Unable to Establish Connection…

I’m thinking it has something to do with that EULA, Steam and Amazon. I guess the server isn’t receiving that Agree option from Steam… But then times out after about 30min.

Thoughts?

Hi All,

Did you see this in the patch for 1.0.5?

The fixes listed below are tentative fixes and mitigations. Our goal is to get these changes out and see if issues persist, so we can continue to work on them and address in a future update if necessary.

Implemented a change to help us dig into the "timed out while waiting for server to describe world" issue, and added a fix to reduce occurrences of this issue while we continue to investigate.

Source: New World Update 1.0.5