PS4 -Dressing Room error playing EASHL

This would make sense because  a few posts ago someone was saying he had to play the game within 5 minutes, I sure as heck can't sit in lobbies more then 2 minutes myself or I will error.

@poqwe

I'm using DNA also but I'm using 4G mobile broadband connection. Are you using DNA cable connection? My friend is using it and he is having this issue.

If you have telnet or something like that available, you can try make a simple connection test:

telnet 159.153.21.158 443

and see if that gets timed out in a few minutes.

@EA_Roger

@NHLiveSupport

@iqqmuT

Yes, Cable connection..

...and I was able to see the same 5min behaviour from my laptop PC by opening he telnet connection and running WireShark.

After 5min it's closed or somehow unreachable (I really don't know much about using WireShark 🙂 )

So it is some related to ISP but EA could anyway do something in the next patch to make NHL 19 handle the possible dropping of long time idle connection as it seems to be a wide spread problem and not just me or just a single operator in Finland.

Im not great with computers n stuff but is there anyway i can see if thats my issue?

@iqqmuT I'm assuming this is complicated but on my PC would I be able to mimic traffic as if it were coming from my PS4 on the connections that need to stay open so they don't time out?

Also for those tired of watching a full test your connection run through, quickly unchecking/rechecking the Connect To Internet box in the network menu does the same thing

@colt45711  I don't know any easier way to test it but using some tools like telnet. 😕 It would nice to have a simple online tool to test idle timeout issue.

@Jpmarchick  Unfortunately you can't have any else workaround for this timeout issue but to try to use some other internet connection.

I wrote an online tester for the timeout issue, can you guys tell what is your result?

Hope the tester works correctly! 🤓

Update: online tester did not work

@poqweThanks for testing the tool! I don't have a faulty connection, so I'm not sure if it works correctly. I sent you a private message so we can discuss more about it.

Update: The online tester did not work.

@EA_Roger@NHLiveSupport

I opened https://159.153.21.158 (in my case NHL 19 was using that server) with my browser and I noticed that it generates Keep-Alive HTTP header in the response:

Keep-Alive: timeout=120, max=731

@EA_Roger@NHLiveSupport

I went to my friend's home where this issue occurs. I tested that all idle TCP connections got cut within 10 minutes. I used Linux router with WireShark to capture all network while the Dressing Room error occurred. If you are interested in the network capture files (pcap-ng), send me a private message and I will share them!

Anyway, it definitely looks like the problem has to do with idle TCP connections that are cut. Related to this error, especially the https connection to 159.153.21.158 seems to be vital (at least in my area). If it fails, Dressing Room error is displayed.

While I was testing, I saw a new error, I have no idea if this is related to the same issue or not. I have a network capture logs from this also. (Sorry about Finnish 🙂

Suggestion #1

I noticed that NHL19/PS4 does not send TCP Keep-Alive packets, they would keep the connection alive. I was thinking if Xbox is sending those packets, maybe that's why it doesn't have the issue.

Suggestion #2

Better error handling when HTTPS connection is dropped. Reconnect if needed.

We don't have an update on this as of yet on our side of things and we are continuing our investigation. Once again, I know you don't see the actual progress on your end but all of the data you've provided so far has helped us progress a lot. I'll check if our devs & QA still need further information from you at this time & s soon as I'm able to give you specifics I will update you.

The workarounds provided here seem to help certain players, which is why I'm encouraging you to try them on your end. We aren't dismissing the issue at all, or claiming it's up to you to find the solution, we just want you to try these workarounds in case they help you.

Thanks,

Roger.

Thank you @EA_Roger for taking the time to update everyone. Obviously everyone is hoping to just be able to play the game within the near future.

I wrote a little tester for idle connections (this time it should work) for Windows/Mac/Linux.

[Random .exe link Removed - Admin.]

It creates a tcp connection, idles given time and checks if the connection is still alive. While it's idling, you can grab a beer and listen to Bee Gees - Stayin' Alive. Some noticed that 5 min idling works but with 6 min idling the connection gets killed. Anyway, if the result is that your connection fails within 30 minutes, your NHL19 most probably has the DRE syndrome.

@iqqmuT

While your intentions may be sound, please understand why I have had to remove your link. Thanks.

You guys don’t know what you’re doing do you? You should probably put some job offers out to some of the guys in the forums who did the actual work for you. Least you could do is update the game. The support for this is pathetic from a company as large as EA. 

Roger? Well Roger it certainly seems like you’re sitting on your a** and twiddling your thumbs cause if this is the one you work at, I’m not sure how anything ever gets done. The whole of EA is trash with your constant errors. I want a refund and a game that actually works. Have only been able to play once tonight out of 30 tries. Send me a refund and a game that actually works. Trash company - hands down.

Try this:

Make sure to launch a new match as quick as you can after starting World of CHEL, preferably within 6 minutes. After the match, exit World of CHEL back to NHL19 main menu.  This method works for my friend who gets DRE.

This prevents tcp connections from idling for too long time and getting timed out.

---

@iqqmuT wrote:

Try this:

Make sure to launch a new match as quick as you can after starting World of CHEL, preferably within 6 minutes. After the match, exit World of CHEL back to NHL19 main menu.  This method works for my friend who gets DRE.

This prevents tcp connections from idling for too long time and getting timed out.

---

I've been doing this 2 weeks ago, but it worked very very rarely. But for other people it might be useful.