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.
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.