Question / Help OBS Dissconect

Narcogen

Active Member
20:58:55.529: socket_thread_windows: Received FD_CLOSE, 9 ms since last send (buffer: 0 / 400384)
20:58:55.529: socket_thread_windows: Aborting due to FD_CLOSE, error 0
20:58:55.532: [rtmp stream: 'adv_stream'] Disconnected from rtmps://rtmp-api.facebook.com:443/rtmp/


20:59:07.349: RTMPSockBuf_Fill, recv returned -30848. GetSockError(): 0 (The operation completed successfully.)
20:59:28.011: RTMPSockBuf_Fill, recv returned -30848. GetSockError(): 0 (The operation completed successfully.)
21:00:08.951: RTMPSockBuf_Fill, recv returned -30848. GetSockError(): 0 (The operation completed successfully.)
21:01:29.938: RTMPSockBuf_Fill, recv returned -30848. GetSockError(): 0 (The operation completed successfully.)
21:09:32.599: RTMPSockBuf_Fill, recv returned -30848. GetSockError(): 0 (The operation completed successfully.)
21:09:32.599: Output 'adv_stream': Reconnecting in 10 seconds..
21:09:32.600: [rtmp stream: 'adv_stream'] Connection to rtmps://rtmp-api.facebook.com:443/rtmp/ failed: -3


Your network connection is having trouble maintaining a stable connection. Wireless is not recommended for streaming.

https://obsproject.com/wiki/Dropped-Frames-And-General-Connection-Issues
 

correabuscar

New Member
if you get these two lines in obs log:
RTMPSockBuf_Fill, recv returned -30848. GetSockError(): 0 (The operation completed successfully [rtmp stream: 'adv_stream'] RTMP_ReadPacket error: 0
and you're trying to stream on kick.com then this simply means that your output resolution is set higher(eg. 2560x1440) than kick supports/allows, so try 1920x1080 instead, which you can do in either of these two ways:
Settings-Output-Streaming-Rescale Output[v] - 1920x1080
capture_004_16032023_110304_bios3004_win11pro.jpg

or
Settings-Video-Output (Scaled) Resolution - 1920x1080
capture_005_16032023_110328_bios3004_win11pro.jpg


In my case 2560x1440 was causing those errors and constant reconnect attempts(every 2-5 seconds) without ever going live, and it made me think it was a network/firewall issue but it is not; so setting 1920x1080 (in either of the above two ways, that is) actually worked, instantly!

Adding this here because google points to it and this is the solution that I was looking for.
 
Top