search

bluenviron / mediamtx

Ready-to-use SRT / WebRTC / RTSP / RTMP / LL-HLS media server and media proxy that allows to read, publish, proxy, record and playback video and audio streams.
MIT License
12.49k stars 1.55k forks source link

WHEP Source auto reconnection #3062

Closed tiz47 closed 9 months ago

tiz47 commented 9 months ago

Which version are you using?

v1.5.1

Which operating system are you using?

Describe the issue

proxied whep source stop working after stopping the whep stream. and it doesn't start again until mediamtx is restarted

Describe how to replicate the issue

  1. create a path (whep-test), with whep source
  2. read with vlc with rtsp
  3. stop the whep stream
  4. start the whep stream again
  5. vlc is unable to read the stream via rtsp
  6. deleting and recreating the path doesn't fix it, the path remains broken

trying with rtmp source instead of whep works without problems.

Did you attach the server logs?

yes

2024/02/23 15:52:50 INF [RTSP] [conn 10.0.0.2:20016] opened
2024/02/23 15:52:50 INF [RTSP] [conn 10.0.0.2:20016] closed: no one is publishing to path 'whep-test'
2024/02/23 15:52:50 INF [RTSP] [conn 10.0.0.2:20017] opened
2024/02/23 15:52:50 INF [RTSP] [session f62d4d7c] created by 10.0.0.2:20017
2024/02/23 15:52:50 INF [RTSP] [conn 10.0.0.2:20017] closed: invalid URL ((null))
2024/02/23 15:52:50 INF [RTSP] [session f62d4d7c] destroyed: not in use
2024/02/23 15:52:50 INF [RTSP] [conn 10.0.0.2:20018] opened
2024/02/23 15:52:50 INF [RTSP] [conn 10.0.0.2:20018] closed: EOF

Did you attach a network dump?

no

RouquinBlanc commented 9 months ago

Getting the same issue in a setup where 2 mediamtx instances are connected via WHEP over the internet:

CLIENTS --RTSP/local--> MEDIAMTX --WHEP/internet--> MEDIAMTX --> source (whatever, but mostly RTSP)

clients fail to get video via RTSP after a while, which we have associated mostly with a restart of the distant instance, but potentially also a temporary loss of connectivity without restart.

github-actions[bot] commented 7 months ago

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

github-actions[bot] commented 1 month ago

This issue is being locked automatically because it has been closed for more than 6 months. Please open a new issue in case you encounter a similar problem.