"Error Loading Player: No Playable Sources Found" despite upgrading to Premium to stream HLS
Hello I am running into an " Error Loading Player: No Playable Sources Found" despite upgrading to Premium to stream HLS. I read that HLS is only supported on Premium accounts. The link I am trying to stream from is http://nuc.smbox.co:8123.
My name is Alex and I am one of the Team Leads of the Support Team at JW Player. I will be more than happy to assist you with your questions.
I can confirm that your account is a Premium account, so that shouldn’t be the problem. Is the actual HLS stream URL http://nuc.smbox.co:8123/ ? If so, that may be the cause of it. If a stream’s URL doesn’t end in .m3u8, our player can’t automatically detect that it’s a HLS stream. You can get around this by adding the type: “hls” configuration option to your setup.
If you continue to have issues, please supply me with a link to a reproduction page so I can see what’s going on.
It looks like you found where to add type: “hls”. As for the “Crossdomain Access Denied” error, some files (including HLS manifests) require the domain that is hosting the file to give the domain in which the page requesting the file resides authorization to use it. This means that nuc.smbox.co:8123 would have to implicitly allow whatever domain you’re hosting your site on (or demo.jwplayer.com in the instance of our Stream Tester) access.
When the player is rendered in Flash, the browser looks for a crossdomain.xml file at the root of the domain hosting the file. You can see this on the Stream Tester when unchecking the “Attempt to render in HTML5” box because this error is printed to the browser’s console:
GET http://nuc.smbox.co:8123/crossdomain.xml 404 (Client error)
So, the browser is trying to request http://nuc.smbox.co:8123/crossdomain.xml in order to see if demo.jwplayer.com is authorized to use the file, but cannot find crossdomain.xml, so the “Crossdomain Access Denied” error appears.
A similar thing happens when the player is rendered in HTML5, but this time the browser looks for the CORS headers on the domain hosting the stream. If those headers either don’t specify the exact domain trying to request the file, or isn’t set up to allow any domain access, an error like this will be printed into the browser’s console:
Fetch API cannot load http://nuc.smbox.co:8123/. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://demo.jwplayer.com' is therefore not allowed access.
To resolve these issues, I would recommend contacting whomever is responsible for nuc.smbox.co:8123 and let them know about the trouble you are running into. You can also find our more information about Crossdomain File Loading on this support article.
Please let me know if you need any more help or have any other questions.
This question has received the maximum number of answers.