Jump to content
The Lotus Eaters: Share Bug Reports and Feedback Here! ×
  • 0

Help fixing stubborn 10054 chat disconnect


Blau-

Question

(Skip to the end for the resolution we found)

Hey hey, I've run across a bunch of threads about this bug, I've tried pretty much everything I can find / think of and I'm not sure what else to try. 

I've already contacted support, and they just gave me copy-paste of the helpdesk article, which was not as helpful as I was hoping. Maybe you guys have some other ideas or can catch something I missed.

Apologies in advance for the wall of text but I wanna be thorough. I'm hoping that if we can resolve this issue for me, it can be helpful for someone else too.

The error:
After a time of chat inactivity (sitting on an inactive chat tab, running a solo mission, running a mission with a squad that is not talking in chat; about 5 minutes worth of inactivity) chat seems to silently drop. After that, I can't see any messages anyone sends (confirmed via running missions with friend in Discord who can see messages, while I cannot). 
Sending a message or switching to an active chat tab spits out the error:

Quote

An existing connection was forcibly closed by the remote host. ERROR 10054

Successfully reconnected to chat server.


and after that, chat works again, until another period of inactivity, in which case it drops and the cycle repeats.

This does not interrupt gameplay. I'm not dropped from missions or kicked from the game. 

What I'm pretty sure is happening is that, somewhere in my local connection, if the chat connection is not kept active enough, the connection is closed, then reopened when some criteria is met (squad sending messages does not reopen it but opening trade chat tab does, for example).

I played the game on my current network connection previously (read: 2018; i took a long break) and did not have this chat issue. My network hardware has changed since then, though.

From EE.log:

Quote

1555.027 Script [Info]: ChatRedux.lua: Chat: Filters for T_EN_NA:
1555.032 Net [Info]: IRC out: JOIN #T_EN_NA
1555.087 Net [Error]: Unhandled socket recv error: An existing connection was forcibly closed by the remote host. ERROR 10054
1555.101 Script [Info]: ChatRedux.lua: Chat: Filters for C51b4c36a07c56ff429001ac7:
1555.102 Net [Info]: IRC out: QUIT :Logged out of game
1555.263 Net [Error]: IRC connected: TLSv1.3 TLS_AES_256_GCM_SHA384
1555.402 Net [Info]: IRC out: NICK Blau|Rascon
1556.152 Net [Info]: IRC out: JOIN #T_EN_NA
1556.152 Net [Info]: IRC out: JOIN #A56cd1e8206c56fdcaad84819
1556.152 Net [Info]: IRC out: JOIN #C51b4c36a07c56ff429001ac7
1556.152 Net [Info]: IRC in: :irc1.warframe.com 005 Blau|Rascon LINELEN=512 MAXLIST=b:4096 MAXTARGETS=20 MODES=20 NETWORK=war-irc2 NICKLEN=54 OVERRIDE PREFIX=(ohv)@%+ SAFELIST STATUSMSG=@%+ TOPICLEN=307 USERLEN=64 WHOX :are supported by this server

And I mean, I could just ignore it and live with it, but this is getting really old. Plus I need to communicate with my squad!

15dijAQ.png

What I have tried so far, that has not helped:

  • Rebooting all involved hardware (my desktop; Archer A7 router; D-Link 520b modem)
  • Updating firmware on network hardware
  • Switching my game region back and forth (currently set to North America, where I am)
  • Enabling Region / Trade chat (i don't usually have these enabled, but having an active chat tab does help -- however, since these don't show up in missions, it defeats the point. My squad/alliance is not very active in chat)
  • Enabling / Disabling IPv6 chat (currently enabled)
  • Enabling / Disabling UPnP (currently enabled; network hardware also enabled)
  • Enabling / Disabling NAT-PMP (currently enabled)
  • Swapping UDP ports
  • Setting up Port Triggering for the UDP and TCP ports the game uses (this seems to fix the issue for most other people, but has not resolved it for me)
  • Swapping between Ethernet and Wifi (currently on wifi, ethernet cable is trash)
  • Setting my router to Access Point only mode 
  • Disabling firewall on Modem and Router
  • Ensuring Warframe is allowed through my desktop's firewall
  • Disabling QoS on router/modem
  • Running Warframe, the launcher, etc. as administrator
  • Optimizing download cache
  • Clearing Steam's cache

(edit: i feel i need to point out that chat uses TCP ports 6695-6699 to my knowledge, so those are the ports that i'm messing with -- it does not use UDP so i've taken those out of my equations)

Connecting my computer to my phone's hotspot does not seem to trigger the issue, which makes me pretty certain it's somewhere in my network.

I have not contacted my ISP for help, since 1. I'm not using their stock hardware, and 2. they've proven to be pretty useless when I contacted them for other reasons in the past.

I'm going to keep tinkering with settings in the meantime, but I'm hoping you folks can help me out. 

 

EDIT 2: 

Support recommended that I test with a VPN to see if the chat issue persists, and so far, a VPN seems to be solving the issue.

This all but confirms that the issue lies in my ISP somewhere, so it's out of my hands. I'll be using a VPN to play from now on. 

My recommendation is, if you get this chat error, you've tried everything you can think of and it seems to be an ISP fault, consider testing with a VPN, and if that seems to fix it, contact your ISP to let them know there's something wrong. 

Link to comment
Share on other sites

2 answers to this question

Recommended Posts

I had this issue a few months ago. However, my issue was ISP related, ie the problem was with my ISP than the game or my router.

It was only fixed after a city-wide blackout, caused by a failing transformer. We had backup generators, but they have a delay when starting. After the 5 hour blackout, my ISP's proxy server restarted (twice now). I started up the game as my router's online now and to my surprise, the chat got fixed.

Their servers needed a restart I suppose.

Since you have done most of the things I would have asked, I think your issue is ISP related here again. In which case, there's not really much we can do about it.

Link to comment
Share on other sites

That's what I was afraid of. It's at least a relief knowing it's out of my hands, but frustrating because my ISP has been less than helpful for prior issues. (telling me to reboot my router when i reported a bad hop in another state like that was going to help)

Any tips for getting through to them without doing the song and dance of "turn it off and back on again"?

 

edit to avoid double-posting forum sin:

Support got back to me and recommended I try out a VPN to see if that helps, and so far, it is helping. This pretty much confirms that it's an ISP issue, so I'll be using a VPN to play until my ISP gets around to fixing the issue (read: probably from now on).

I edited my initial post to help anyone who might also be having the issue, to let them know to try out a VPN if they've tried everything else. 

Cheers and good luck!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...