Question / Help Is this error Facebook's fault or mine? WriteN, RTMP send error 10054 (117 bytes)

[Murray]

Hi,
It looks like I was disconnected twice during this 45 min stream (streaming zoom and pre-recorded videos) not gaming.
after each disconnect the video turned into a slideshow for many minutes and missed a bit of content in one case, I guess while things caught up?
I looked at the do this first post but I've streamed before, and since, without these issues.
So I wonder if it's a one-off?
This is/was mothers day morning, perhaps FB ingestion servers are over-loaded.
My main question: from the error number can you determine what the issue is, and is there anything I can do at my end or is it not my fault?
Or is it not my fault but I could still do something at my end?
Facebook offers "Use a backup stream" but I don't see how to use 2 stream keys in OBS
Also: I can't tick any of the boxes in Settings > Advanced > Network

Thanks for your help.

Here's the full log
But I think this is the relevant bit:

10:10:51.886: WriteN, RTMP send error 10054 (387 bytes)
10:10:51.887: WriteN, RTMP send error 10054 (117 bytes)
10:10:51.887: WriteN, RTMP send error 10038 (42 bytes)
10:10:51.887: [rtmp stream: 'simple_stream'] Disconnected from rtmps://rtmp-api.facebook.com:443/rtmp/
10:10:51.887: Output 'simple_stream': stopping
10:10:51.887: Output 'simple_stream': Total frames output: 48727
10:10:51.887: Output 'simple_stream': Total drawn frames: 48874 (48882 attempted)
10:10:51.887: Output 'simple_stream': Number of lagged frames due to rendering lag/stalls: 8 (0.0%)
10:10:51.887: Output 'simple_stream':  Reconnecting in 10 seconds..
10:10:51.957: warning: 2 frames left in the queue on closing
10:11:01.945: [jim-nvenc: 'simple_h264_stream'] settings:
10:11:01.945:     rate_control: CBR
10:11:01.945:     bitrate:      6000
10:11:01.945:     cqp:          20
10:11:01.945:     keyint:       120
10:11:01.945:     preset:       hq
10:11:01.945:     profile:      high
10:11:01.945:     width:        1920
10:11:01.945:     height:       1080
10:11:01.945:     2-pass:       false
10:11:01.945:     b-frames:     2
10:11:01.945:     lookahead:    false
10:11:01.945:     psycho_aq:    true
10:11:01.945:
10:11:01.954: ---------------------------------
10:11:01.954: [FFmpeg aac encoder: 'simple_aac'] bitrate: 128, channels: 2, channel_layout: 3
10:11:01.954:
10:11:01.956: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmps://rtmp-api.facebook.com:443/rtmp/...
10:11:02.124: [rtmp stream: 'simple_stream'] Interface: Intel(R) Ethernet Connection (2) I219-V (ethernet, 1000 mbps)
10:11:03.987: [rtmp stream: 'simple_stream'] Connection to rtmps://rtmp-api.facebook.com:443/rtmp/ successful

 

[sarahbitethis]

I had this same problem for over a month on twitch. I fixed it by changing the MTU on the PC

 

[sarahbitethis]

I had this same problem for over a month on twitch. I fixed it by changing the MTU on the PC

I meant to put the info, my bad. But you can change it pretty easily in cmd. I have an article that shows exactly how to find the correct number, but it leaves out what to do beforehand.

1. Open cmd as admin and type netsh interface ipv4 show subinterfaces
2. Check the number on the same line as your network adpater (Ethernet/Wi-FI), usually its1500
   • If its not 1500, change it to it because its the most accurate baseline. You can do this by using netsh interface ipv4 set subinterface “Name of Adapter” mtu=1500 store=persistent (Name is under Interface of the first command)
3. After thats established follow the steps in this article https://hide.me/en/knowledgebase/how-to-find-correct-mtu-values/
4. After that (make sure you add 28) change the MTU using the same command netsh interface ipv4 set subinterface “Name of Adapter” mtu=(number) store=persistent
5. Once thats set you can go ahead and type netsh winsock reset and netsh int ip reset then reset the PC. Not required but kind of a full refresh of the network, so just a mention

I tried just about everything to fix the problem and this ended up doing it. I did change some other things as well so it IS possible this in combination of something else worked, but I did this after I fully reinstalled Windows. I really hope this helps because this info wasn't found anywhere really until I came across someone that changed his to 1400 and was able to stream again. Its not in any troubleshooting suggestions anywhere.

Hope this helps, take care

 

[WBE]

Attached a screenshot of https://hide.me/en/knowledgebase/how-to-find-correct-mtu-values/ after reported unavailability issues (in another thread pointing to this solution).