Question / Help 10054: anyone figured it out?

[CrillFactor]

I'm trying to help two friends in Seattle who live in the same house, and all of their RTMP connections to Twitch, Restream and/or Beam will frequently and randomly reset with the rare 10054 error. Using a non-RTMP protocol (FTL) to broadcast to Beam works flawlessly. As far as I'm aware 10054 means the server disconnected them, but can anyone shed any light on why it does this? It seems like every thread where it does pop up, the issue is unresolved or a completely different connection is used. Is there a good resource to consult about this?

 

[dodgepong]

Disconnections come from network issues, possibly some sort of network instability or interruption. The best thing to do is to try a different server and follow this thread: https://obsproject.com/forum/threads/dropped-frames-disconnecting-lag-read-this-first.8870/

 

[Solon]

No dice with the usual disconnection solutions fixing this. We've done it all and the error happens totally inconsistently every 5 to 45 minutes. Both computers (running Win7 and Win10) have this problem every time /except/ when we stream with non-RTMP protocols. Streaming on Beam.pro using Tachyon's FTL protocol was no problem for our six hour test.

I've attached my log files for review. Any ideas??

 

[Suslik V]

Network issues (connection or hw) on server side or your stuff.