-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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] Can't load the video on this Invidious instance. YouTube is currently trying to block Invidious instances. #4045
Comments
Please post the invidious version (bottom of the page) and check if you are up to date. |
I'm running the latest image, from 3 days ago |
Please post the version anyway thank you. And the video ID where you have these errors. |
I'm chiming in with +1 on this issue - 403 on Container logs say the same:
Version: Affected IDs: |
@swolford funnily enough, all of those videos play on my instance. And whenever I encounter the 403 error, I just hit the "switch invidious instance" and they pretty much always work on another one. Also, I just tried the video that was failing on my instance yesterday and it's working now. So it's definitely just an intermittent issue. But once it starts failing on an instance, it keeps happening even after hard reloading, restarting the instance and even updating it. I think this might be related to the communication to youtube itself |
I'm guessing it might be a cache issue. YouTube recently implemented a change that broke playback as various streaming urls returned will just yield a 403 instead of actual video content. See #4027 A workaround was added in #4037 which was merged on August 7th. However, due to the video cache, streaming urls from before the fix are still being used. The aforementioned video working now is probably because the cache got cleared. |
I guess I'll leave this open for a couple days then and see if the error resurfaces. If not, I'll close this issue |
I have it with almost all videos on my personal instance. Latest image also. Edit: all new videos do not work - very strange! |
Rebuilding the Dockerimage and running docker-compose again made it work for now. |
I don't think so the cache is only kept for 6 hours max and refresh by invidious after that. |
I can affirm that this issue occurred in previous versions, rebuilding (through |
I haven't encountered the issue at all in the past few days, so I'll close this as resolved. |
I'm getting this error on https://iv.nboeck.de, https://vid.puffyan.us, https://invidious.io.lol, https://invidious.no-logs.com instances |
Reopening as youtube appears to straight block the IP addresses of the popular public instances. |
The issue #3915 still applies for discussing about how to circumvent youtube blockage. Please see how to circumvent the blockage: #4045 (comment) |
Youtube might be blocking subnets, I get a 403 on IPv6es in both the 16 IPv6 and routed subnets of BuyVM Luxembourg. I also will try (re)setting up the ipv6 thing on my home network and trying with that, to see if that will help. The interesting part in all this is that Piped continues to work, with all the IPv6es I threw at it after this wave of blockages.. |
Most instances currently are IP blocked specifically when it comes to proxying video: iv-org/invidious#4045
Closing in favor of #4734 |
EDIT: Switched title from
Constant 403 errors while trying to load videoplayback
toCan't load the video on this Invidious instance. YouTube is currently trying to block Invidious instances.
in order to reflect the current error message.EDIT by @unixfox: It appears that youtube is trying to block the popular invidious instances by returning 403 if the video stream is loaded through the invidious instance (with proxy or dash enabled).
Alternative solution is to switch off proxy or use another instance that is unblocked.
To public instances maintainers: #4045 (comment)
Describe the bug
I host my own invidious instance and some videos just won't load on it. The thumbnail loads, but the video itself does not. There's just a spinner and the timeline says 0:00/0:00. This does not happen with all videos, but I haven't spotted a pattern yet.
When looking at the network tab, I can see that the browser is constantly sending requests to
/videoplayback
and getting a 403 status with no response body. It sends about 10 requests per second and doesn't stop until I close the tab. For reference, I use DASH on my instance.Steps to Reproduce
Logs
Logs don't show anything besides the failing request log itself:
Screenshots
Additional context
docker-compose.yml file:
The text was updated successfully, but these errors were encountered: