Connection interrupted after exactly 5 hours

[ChemoKnabe]

I'm encountering a strange problem when streaming on Twitch, which I can't solve myself. The stream runs smoothly during the entire transmission time, but breaks off exactly after 5 hours.

Symptoms:

• Viewers receive the Twitch network error code.
• The OBS stream cannot be ended even though it shows 0 kb.
• A hard shutdown of the OBS client via the task manager and a restart are necessary.
• After the restart, the stream continues to run without further interruptions.

Log entries:
21:36:03.701: [obs-websocket] [WebSocketServer::onClose] WebSocket client `[::ffff:192.168.0.10]:50765` has disconnected with code `1000` and reason: User requested disconnect
22:44:35.884: socket_thread_windows: Increasing send buffer to ISB 1048576 (buffer: 0 / 788480)
22:45:20.691: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:192.168.0.10]:50926
22:45:20.891: [Lua: OBS-Stats-on-Stream.lua] Profile Config loaded: C:\***\basic.ini
22:45:20.893: [obs-websocket] [WebSocketServer::onClose] WebSocket client `[::ffff:192.168.0.10]:50926` has disconnected with code `1000` and reason: User requested disconnect
22:45:20.898: [Lua: OBS-Stats-on-Stream.lua] Profile Config loaded: C:\***\basic.ini
22:45:21.132: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:192.168.0.10]:50927
22:45:21.324: [obs-websocket] [WebSocketServer::onClose] WebSocket client `[::ffff:192.168.0.10]:50927` has disconnected with code `1000` and reason: User requested disconnect
22:45:22.016: socket_thread_windows: Received FD_CLOSE, 46182 ms since last send (buffer: 0 / 788480)
22:45:22.016: socket_thread_windows: Aborting due to FD_CLOSE during shutdown, 0 bytes lost, error 0
22:45:22.392: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:192.168.0.10]:50931
22:45:22.585: [obs-websocket] [WebSocketServer::onClose] WebSocket client `[::ffff:192.168.0.10]:50931` has disconnected with code `1000` and reason: User requested disconnect
22:45:22.850: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:192.168.0.10]:50932
22:45:23.135: [obs-websocket] [WebSocketServer::onClose] WebSocket client `[::ffff:192.168.0.10]:50932` has disconnected with code `1000` and reason: User requested disconnect
22:45:28.141: [rtmp stream: 'adv_stream'] User stopped the stream
22:45:28.141: Output 'adv_stream': stopping
22:45:28.141: Output 'adv_stream': Total frames output: 1077190
22:45:28.141: Output 'adv_stream': Total drawn frames: 1077304 (1077309 attempted)
22:45:28.141: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 5 (0.0%)
22:45:28.161: ==== Streaming Stop ================================================
22:45:39.053: ==== Shutting down ==================================================

 

[ChemoKnabe]

Push

 

[PaiSand]

Please post a log with your issue! Here's how...

OBS Studio creates a log file each time you run it which contains very useful diagnostic information. Without a log file, it's much harder for any support volunteers to figure out problems and your post may be ignored. To upload a log file, go to the Help menu > Log Files > Upload Last Log...

obsproject.com

Errors on Twitch must be asked to their support.
The error #2000 on Twitch streams is known and many people suffer from it (including me). I used the report error on the player settings but who knows when they are going to address this problem and if it's easy to fix.

If you can't end the stream is due to a bad behavior from a plugin. Or at least is the most common culprit on this issue.

By the way, it's BUMP (acronym), not push.

 

[ChemoKnabe]

But this problem also occurred when I wasn't using any plugins.

It would also be strange if Twitch crashed at the same time as a non-existent plugin, wouldn't it?

I prefer push xD