-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Bug] DASH playback shows "media could not be loaded" with videos longer than ~ 1 minute #4884
Comments
OK, it looks like this was an issue caused by my po_token. I had generated it correctly, but I tried again and noticed that on another network, I got a much longer token output than before. About twice as long. I'm going to go over to the repo for the There's still an issue here, but I have luckily managed to generate a po_token that works. I'm guessing it's something on Youtubes' side trying to prevent the tokens being generated in invalid situations. |
Describe the bug
I've updated to the latest version after getting the "this helps our community" error.
Now, when using DASH, on videos longer than about a minute, I get the "media could not be loaded" error. The limit isn't exactly a minute, but anything over about 1:20 gets the error, I've tried dozens of videos to confirm this. The error shows up as soon as the page loads, but only for those videos with a runtime longer than a minute. The short videos play fine.
I have:
quay.io/invidious/youtube-trusted-session-generator
on the same server with the same IPI've also added some debug lines and compiled/run invidious with some custom stuff to see where it's getting to. It's the responses from
***.googlevideo.com/videoplayback
calls that 403. I've also confirmed that the calls to googlevideo endpoints include thepot
andn
query params with the values that came from thepo_token
and the sig-helper respectively.Using non-dash mode works perfectly.
Steps to Reproduce
Unsure whether it's reproduceable - happy to help with any details though
Logs
Let me know if I should provide the 403 log lines from the container, and whether anything needs to be exclude from it.
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: