PS4 -Dressing Room error playing EASHL
Product: NHL 19 Platform:Sony Playstation 4 How often does the bug occur? Often (50% - 99%) Steps: How can we find the bug ourselves? Not sure What happens when the bug occurs? when loading in...
Forum Discussion
I don't have this issue normally but I was able to reproduce it in Finland.
I made a router from a Linux machine between PS4 and WAN and I was tracking connections that EASHL is making. EASHL created TCP connections to 159.153.21.158 port 443 (https) and some of these connections were idling. They had traffic again when starting a match successfully. While these connections were idling, I dropped these connections with iptables and I was able to see the error when starting a new match.
Steps I did:
- Start CHEL
- Track TCP connections that are idling (having no data transfer for some time)
- Drop/Reject those idling connections with iptables (using --reject-with tcp-reset flag)
- Starting a match from dressing room (I was in EASHL Drop in), the error is displayed: "DRESSING ROOM ERROR Dressing Room found an unexpected error. Please try again."
If you are interested in more detailed instructions, contact me. So most probably those who experience this issue, have an internet connection where idle TCP connections are dropped by a timeout. Changing a router or using DMZ does not help if the timeout is defined by internet provider.
Fix Suggestion for EA
Handle HTTPS connection errors better in NHL19. When making a query using an existing connection and it fails (due to timed out and dropped connection), make a new connection and retry the query.
Im not great with computers n stuff but is there anyway i can see if thats my issue?
@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
- Hmmm... according to the tester it didn’t timeout at 5min or 10min :o
Are you sure it works? 🙂 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
I don't really understand how this could cause the issue for some but not for all, but anyway is it possible to try to increase the value to 3600 or so and see if it happens to have any effect? However, it can cause performance problems like the documentation says: https://httpd.apache.org/docs/2.4/mod/core.html#keepalivetimeoutI 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.
EA_RogerEA Staff (Retired)
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 officially give up. If you cant fix a problem in 2 weeks, something is wrong.
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.
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.
- Have to agree updates it’s got worse! 2 games played in 3 hours of trying last night
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.
