about 1 year ago - HybridLyte - Direct link

You can try these potential fixes on our Tech Support page
https://support.lastepoch.com/hc/en-us/sections/1260801697069-Crashes-Hangs

Thanks for the reports though, any additional information you can give about reproducing these issues would be a major help.

about 1 year ago - HybridLyte - Direct link

Are you just unable to load into the game or are they consistent client crashes?

about 1 year ago - HybridLyte - Direct link

Players being unable to get into Online is a separate issue we’re tracking currently. The client crashes appear to potentially be a separate issue. Hopefully once the connection issues clear up the crashing issue will be easier to spot.

about 1 year ago - HybridLyte - Direct link

Working on passing all this info along to the team. All the additional info will be a major help.

about 1 year ago - HybridLyte - Direct link

If you could post your Player.Log files from here: C:\Users[USER]\AppData\LocalLow\Eleventh Hour Games\Last Epoch

That’d be a great help.

about 1 year ago - Hackaloken - Direct link

Hi there,

I’m sorry that we don’t have a solution here. Unfortunately I don’t think this problem applies in this situation: the players that needed to contact their ISPs about these addresses were unable to get past the Login / Play Online screen, whereas it appears that everyone in this thread is able to get to the character selection screen.

Also, if that was the problem, I would expect to see this in your Player.log: Curl error 28: Failed to connect to df4fe.playfabapi.com port 443 after 168405 ms: Timed out. Since it isn’t there, you were able to successfully connect to this address.

Sometimes WinMTR (and similar tools) shows a “Connection Timed Out” because the various points in between you and the destination may de-prioritize or block Ping traffic, while allowing actual traffic through.

It is still possible that this could be an ISP issue, but it’s not related to this load balancer. We’re still investigating. Unfortunately it’s taking a while because our backend/server team is working to address a lot of different concerns right now.