OBS Keeps disconnecting & reconnecting immediately

M

MrPerplexful

New Member
Heyo!

Please see my log file here; https://obsproject.com/logs/7Lkc5pWNjsCG3ldX

I am not sure why but my stream always cuts out an hour into streaming and automatically reconnects.
Its very annoying as it keeps dividing up my VODs on my twitch channel.

Anybody know a solution for the above log file?

I just allowed TCP 1935 port in my firewall as an inbound rule as I read that might help.
Any other suggestions would be greatly appreciated.
 
M

MrPerplexful

New Member
M

MrPerplexful

New Member
Harold said:
https://obsproject.com/wiki/Dropped-Frames-and-General-Connection-Issues covers how to solve connection issues


This advice is flat out wrong, as you are connecting to a remote port 1935, not hosting a server yourself.
Click to expand...
Could it be an encoder issue as well?

I am noticing when looking at the end of my stream the below appears in the log;
- I notice that the bandwith stalls account for much less dropped frames than the encoding lag. This just seems strange considering I have a 3070TI and am using the nvenc encoder.


20:53:27.807: warning: 2 frames left in the queue on closing
20:54:01.163: [rtmp stream: 'simple_stream'] Stream shutdown timeout reached (30 second(s))
20:54:01.163: [rtmp stream: 'simple_stream'] User stopped the stream
20:54:01.163: [rtmp stream: 'simple_stream'] Socket send buffer is 65536 bytes
20:54:01.163: Output 'simple_stream': stopping
20:54:01.163: Output 'simple_stream': Total frames output: 651397 (651439 attempted)
20:54:01.163: Output 'simple_stream': Total drawn frames: 26709
20:54:01.163: Output 'simple_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 42 (0.0%)
20:54:01.163: [rtmp stream: 'simple_stream'] Freeing 1 remaining packets
20:54:01.163: Video stopped, number of skipped frames due to encoding lag: 2383/653808 (0.4%)
 
Harold

Harold

Active Member
The way the connection type works for streaming, you are connecting OUT from your machine.
When you're connecting out in this manner, you are basically NEVER using the same port as on the server end. (there's a 1 in 64511 chance of you actually having the same port, and the next time you connect you're almost guaranteed to not have the same port)

Opening an inbound TCP port (regardless of what port it is) is for when you're running a server, not connecting to one.
 
M

MrPerplexful

New Member
Harold said:
The way the connection type works for streaming, you are connecting OUT from your machine.
When you're connecting out in this manner, you are basically NEVER using the same port as on the server end. (there's a 1 in 64511 chance of you actually having the same port, and the next time you connect you're almost guaranteed to not have the same port)

Opening an inbound TCP port (regardless of what port it is) is for when you're running a server, not connecting to one.
Click to expand...
Thanks! I changed it to outbound, as for my above question would it be possible that this is an encoder overload issue rather than an internet issue?
 
Harold

Harold

Active Member
Not likely. The encoder overload issue is coming from something else and behaves differently
 
M

MrPerplexful

New Member
Harold said:
Not likely. The encoder overload issue is coming from something else and behaves differently
Click to expand...
So the below two lines means this has nothing to do with my internet right? Most likely just an encoding issue?

20:54:01.163: Output 'simple_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 42 (0.0%)
20:54:01.163: Video stopped, number of skipped frames due to encoding lag: 2383/653808 (0.4%)
 
You must log in or register to reply here.
Top