HLS gives HTTP 404 not found

[richard-vd]

Hi,
My RTSP stream plays fine in the embedded player example page (WebRTC). Now I am trying to access this RTSP stream as HLS. From the HLS player examples I understand that I should be able to get the M3U8 playlist at https://<WCS_IP>:8445/<URL-encoded-RTSP-URL>/<URL-encoded-RTSP-URL>.m3u8. However, this fails all the time with HTTP 404 not found from the HLS server. It is the same on the demo server.

 

[Max]

Good day.
We reproduced the issue with RTSP captured streams playback as HLS and raised the ticket WCS-2811 to fix it. We'll let you know results in this topic.
The workaround is to use CDN: capture RTSP stream to Origin server and play it from Edge server.

 

[Max]

We found a simple workaround: you should capture RTSP stream using REST API, for example

curl -H "Content-Type: application/json" -X POST http://localhost:8081/rest-api/rtsp/startup -d '{"uri":"rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov","toStream":"stream1"}'

then play it as HLS

https://<WCS_IP>:8445/stream1/stream1.m3u8

In this case, the stream is played correctly.

 

[Max]

Good day.
We fixed the issue with RTSP streams captured by REST API playback via HLS (WCS-2811) in build 5.2.714.
Now, we raised the ticket WCS-2819 to allow RTSP capturing to play via HLS without intermediate REST API query.

 

[Max]

Good day.
Since build 5.2.771, it is possible to capture RTSP stream without intermediate REST API query as https://<WCS_IP>:8445/<URL-encoded-RTSP-URL>/<URL-encoded-RTSP-URL>.m3u8 . Please update and check.

 

[richard-vd]

Today I updated to 5.2.784 and I can confirm that HLS from an RTSP source now works as expected. Thank you!