-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Playback stops after failed retries with 403 #6741
Comments
Chrome media internals output
|
Hi @daveisfera. Have you tried dev ( https://hlsjs-dev.video-dev.org/demo/)? Is the behavior the same? The media internals are not useful in this case (hls.js is deciding what to load, not the browser's decoder/renderer). We need hls.js console logs (config: |
Yes, I tried the dev site with the same outcome. I included the console output and if I'm understanding that test page correctly, then |
There should be more than just errors. Maybe you're filtering some of the console output? |
Here are some related issues about the retry policy for 4xx errors that may contain some helpful information: |
Yes, I had noticed those issues, but those are a 404 response and I understand that S3 will respond with a 403 for both a missing file and a permission denied, so the 403 is very similar to a 404 in this case, but there technically is a difference and the short retry time of HLS.js is causing a problem here that is handled correctly by Safari and Video.js. Here's the logs from a run that ran into the issue: |
What version of Hls.js are you using?
1.5.14
What browser (including version) are you using?
Chrome 129.0.6668.72 and Safari 18.0
What OS (including version) are you using?
macOS 15.0
Test stream
No response
Configuration
Additional player setup steps
Using https://hlsjs.video-dev.org/demo/ for a minimal reproducer and has to be an actual live stream so a 403 response can be sent for a very short period of time and then a 200/206 returned once it's available
Checklist
Steps to reproduce
Expected behaviour
There would be a slight delay between the retries so it was more meaningful. This is the behavior of both Safari and Video.js
What actually happened?
Immediate retries that all fail and the playback stops
Console output
(you can see that it almost failed the first time but one of the last retries worked and then the second time all of the retries failed and the playback was stopped)
The text was updated successfully, but these errors were encountered: