Hey!
I do live streaming on YouTube.
I am broadcasting to the RTMP server.
Recently, problems have begun. Began to happen every 5 seconds - 5 minutes disconnect, and then reconnect to the server. This is very annoying.

1) Internet is directly connected via cable to PC.
2) I found out and checked everything with the Internet provider, there are no problems on their part.
3) Put a static IP so that there was as much open access to the network as possible.
4) In the personal account of the Internet provider, I completely disabled protection and opened all ports.
5) Added OBS Studio to the list of exceptions in Windows Firewall and Defender.
6) I run the program as administrator.

HLS and RTMPS do not work normally at all, either frame loss or bitrate drops to 0.

With all this, Streamlabs OBS works without problems on the same RTMP and there are no reconnections.
 

Attachments

  • 2021-05-13 16-56-47.txt
    101.6 KB · Views: 53
  • 2021-05-13 17-40-33.txt
    13 KB · Views: 9
  • 2021-05-13 17-41-16.txt
    21.3 KB · Views: 6
  • 2021-05-13 17-42-44.txt
    20.5 KB · Views: 5
  • 2021-05-13 17-45-48.txt
    19.8 KB · Views: 5
  • 2021-05-13 17-52-11.txt
    32.8 KB · Views: 6
  • 2021-05-13 17-55-22.txt
    42.9 KB · Views: 6
  • 2021-05-13 18-24-16.txt
    31.6 KB · Views: 4
  • 2021-05-13 18-40-29.txt
    12.6 KB · Views: 5
  • 2021-05-13 18-40-41.txt
    70.3 KB · Views: 14

qhobbes

Active Member
1. Binding to a manually chosen IP address is rarely needed. Go to Settings -> Advanced -> Network and set "Bind to IP" back to "Default".
2. Create a free restream.io account, connect restream account to YouTube and OBS to restream.

From https://obsproject.com/forum/threads/obs-disconnected-reconnecting-in-a-loop.122285/
If still having issues, disable dynamic bitrate. You might also have 3rd party software interfering, the log is incomplete so it doesn't show what firewall / security software is in use.
18:40:41.452: Sec. Software Status:
18:40:41.453:
18:40:41.453:
18:40:41.453: Current Date/Time: 2021-05-13, 18:40:41

A winsock reset might help, from an admin cmd prompt:

netsh int ip reset
netsh winsock reset
 
Top