Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebRTC Client Doesnt reconnect if stream is interupted #4022

Closed
Taps7734 opened this issue Dec 6, 2024 · 2 comments · Fixed by #4112
Closed

WebRTC Client Doesnt reconnect if stream is interupted #4022

Taps7734 opened this issue Dec 6, 2024 · 2 comments · Fixed by #4112
Labels
bug Something isn't working webrtc

Comments

@Taps7734
Copy link

Taps7734 commented Dec 6, 2024

Which version are you using?

1.10.0

Which operating system are you using?

Windows amd64 standard

Describe how to replicate the issue

  1. start the server
  2. publish with whip from OBS using https://some.servername.com:8889/path/to/stream/whip or pull from a standalone RTSP camera
  3. read with Chrome/Edge/Firefox browser by going to https://some.servername.com:8889/path/to/stream/

If the incoming stream gets interrupted, v1.9.3 and before would continue when the stream was reconnected. Occasionally I would see a message saying it would retry in a few seconds.

In 1.10.0 now it just pauses on the last image before the stream was stopped.

I currently have a task set to run at the top of every hour, which quickly restarts the server and then manipulates the recorded files. So if I am watching the stream at this time, the page has to be refreshed to continue live video.

This also happens if a remote incoming stream has a poor internet connection and drops for a few seconds. Used to be in 1.9.3 and before, it would start a NEW recorded file. Now it keeps recording to the same file when it resumes publishing, but the client stops.

Server logs

No response

Network dump

No response

@aler9
Copy link
Member

aler9 commented Dec 6, 2024

Hello, I can confirm the issue and it is probably a regression caused by #3899.

We need to find a proper trade-off between solving the issue described here and issue described in #3899.

Copy link
Contributor

This issue is mentioned in release v1.11.1 🚀
Check out the entire changelog by clicking here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working webrtc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants