-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
Some of the media could not be downloaded due to a network error #415
Comments
I have same problem, The player stops and gets an error; Secondly; Please help me for this issues. |
I saw a message like the one in the link above, it mentions the hls.js error detail. However, when I examine the ovenplayer codes, I see that the error return message details are missing in the provider section. https://github.com/AirenSoft/OvenPlayer/blob/master/src/js/api/provider/html5/providers/Hls.js hls.js Error Example : {
"type": "mediaError",
"details": "bufferStalledError",
"error":
{
"message": "Playhead still not moving while enough data buffered @37.961094 after 3 nudges",
stack:"Error: Playhead still not moving while enough data buffered @37.961094 after 3 nudges ....",
},
"fatal": true
} OvenPlayer Error Example: {
"code":302,
"message":"Some of the media could not be downloaded due to a network error.",
"reason":"Error occurred when downloading.",
"error":"bufferStalledError"
} That's why I can't see the actual detailed error coming to the player. How can I see the error details ? |
In version v0.10.35, all errors in hls.js were added as follows.
Is the problem of your stream suddenly not playing being caused by the latest update to hls.js? |
I have been using the player for about 6 months without any problem, but in the last week we started to receive the below error message at different times. Video url format HLS multibitrate and server network is stable. What could be the reason ?
{"code":302,"message":"Some of the media could not be downloaded due to a network error.","reason":"Error occurred when downloading.","error":"internalException"}
The text was updated successfully, but these errors were encountered: