I have .m3u8 videos hosted on a local server. When JWPlayer goes to read them I can see in my network trace the requests hitting the server and correctly returning data. The player initially loads (after the .setup() call) but hitting play results in an error:
"Network Error: http status 0"
I'm using the self-hosted api, 7.3.4.
Hello,
Does your stream work in the stream tester from JW Player or Wowza by chance?
Wowza: www.wowza.com/testplayers
JW Player: http://demo.jwplayer.com/stream-tester/
Randy
No, it fails on the stream-tester with the same error. Working on to try on the wowza tester...
In my network stack I can see it grab the initial .m3u8 file:
#EXTM3U
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=1100000
http://<...removed...>1100k.mp4.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=2400000
http://<...removed...>2400k.mp4.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=500000
http://<...removed...>500k.mp4.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=800000
http://<...removed...>800k.mp4.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=3400000
http://<...removed...>3400k.mp4.m3u8
and then I see it grab the 5 individual files with success, but then the error occurs.
I take that back, it's not even reading the m3u8 files now.
playerInstance.setup({
playlist: [{file:video.hlsTablet}],
autostart: true
});
is my setup call, where video.hlsTablet = "http://<removed>...m3u8"
with content:
#EXTM3U
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=1100000
http://<removed>.mp4.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=2400000
http://<removed>.mp4.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=500000
http://<removed>.mp4.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=800000
http://<removed>.mp4.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1, BANDWIDTH=3400000
http://<removed>.mp4.m3u8
K, one more update... even if I point the player at one of the specific bandwidth m3u8's, I still get the issue. Here's the content of the m3u8...
#EXTM3U
#EXT-X-MEDIA-SEQUENCE:0
#EXT-X-ALLOW-CACHE:NO
#EXT-X-VERSION:2
#EXT-X-KEY:METHOD=AES-128,URI="https://<removed>/hls-key/vodkey.bin",IV=<removed>
#EXT-X-TARGETDURATION:8
#EXTINF:8,
eds1_ep103_pr_screener_tablet_360_1100k.mp4Frag1Num0.ts
#EXTINF:8,
eds1_ep103_pr_screener_tablet_360_1100k.mp4Frag1Num1.ts
...<removed>
Alright, some additional info. By hitting that .m3u8's directly in mobile browsers they load just fine. I do not believe this is an issue with those manifests....
So, to wrap this all up. It appears the issue was actually an http/https issue. Even though absolutely NOTHING about anything out of the player would indicate that, getting everything over to https resolved the issue.
Hope this can help someone in the future.
Hello Matt,
Thank you for your thorough analysis. I’m glad you were able to get to the root cause of this and provide your feedback. I’ve had an internal conversation about this as well.
Randy
