-
Notifications
You must be signed in to change notification settings - Fork 886
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
Can't load certain videos #1438
Comments
This might have been a temporary |
It turns out that the problem was only gone on some videos, like the first one I mentioned above, now I got the same behavious on: |
I'm having this issue now. I tried watching 2 videos and even 5 videos from history and they all failed to load. |
I can't play any video right now, all failed to load. |
Same here I am unfortunately unable to play any video 😞 . Did API change? |
same issue here |
I have the same issue. |
I too am seeing this behaviour. In case my location matters; I'm in South West England. |
Same here. |
same here in germany (linux) |
Same here since this afternoon (Netherlands), both on Mac and Linux client. |
Same here in Hong Kong (Linux client) |
Thanks, Invidious playback now works, but the original error ("Local API Error (Click to copy): Error: Status code: 404") still remains |
Pretty sure it has to do with this: fent/node-ytdl-core#939 |
+1 |
I've discovered that every video is now resulting in the 404 error. Age restricted videos began having this issue (after ytdl's fix a few weeks ago) several days back. Changing to the Cyberhost network semi-solves the problem, but as others have said, still brings up the text error while allowing videos to play. It also doesn't solve the issue that age restricted videos have been having, again, for several days, despite that issue only being fixed a couple of weeks ago. UPDATE: After a few minutes of using the Cyberhost URL, it's no longer working for most videos, either. May I ask if YouTube intentionally updates elements of their code on a regular basis to try and throttle third party clients such as FreeTube and the ytdl core, or do they do so simply for improvements to the functioning of their site? Until late last year, when they began a crackdown on the ability to view age restricted content, they'd done very little to affect the functioning of clients to my knowledge. |
Could you guys pls link the the issue here as well? Can't click a link in a picture sadly ;) |
I think this is the issue mentioned |
|
I'm not able to see any video from my subscription list right now. I tried to change the invidious instance but nothing change ! Here are my settings ! |
yewtu.be doesn't work too, I tried. I am using invidious.kavin.rocks |
yewtu.be is working on my side ! even with invidious.kavin.rocks i'm not able to see any video on my subscriptions list ! |
https://invidious.kavin.rocks |
unless i'm very mistaken, he just means "work in progress" |
@realfraze makes sense. It was there last week. I was able to change the video resolution while the video is playing, but now I can't. The option is completely gone |
What u can do tho is post ur comment about resolution here #595 for visibility. |
I can't load any video either. Doesn't even seem to matter what I put in Invidious Instance. |
the same for me ! Whatever instance i put, loads of video doesn't work |
Works for me too. |
@MattRGX @trych - After you change the invidious instance, you need to refresh the video from subscription page to reload the whole thing. If you haven't, you should. |
Nope. Doesn't change a thing unfortunately. Restarting the app doesn't help either. I cannot play a single video, no matter what. |
Quick update: the upstream issue has been resolved and merged. Now its just a matter of time for Freetube to fix the issue on their end. |
Seems to work again for most videos! |
IIRC age restricted videos were already broken before this issue occurred. Its a known problem and is been worked on. This reply was 24/06 |
Ah, ok. Thanks for the info! |
refreshing worked for me. still getting error text but video will play after fallback using https:/yt.cyberhost.uk Thanks |
Hotfix update is available to download: https://github.com/FreeTubeApp/FreeTube/releases/tag/v0.13.2-beta https://freetubeapp.io/#download This should resolve this issue. |
go here and verify a current node is working ON THIS NOTE SECONDLY |
-- #1472 |
See #1296 |
creating a blocklist and/or using a random selection list creates a new hash of problems and errors instead of attempting to automate this process; better Error messaging can be displayed a block selection if automated i specifically choose US based instances due to Latency/ping |
Latency up to to 1000ms is irelevant while playing videos as they get preloaded in a buffer and doesn't require any real time input. Agree with better messaging, but disagree with automatization as the more auomated this is the better since all videos on invidious now require me to use redirect.invidious.io and go through instances which is pita. Also in the world where all instances works pressing the button is still annoying |
I am going to close this, as the original problem was solved with the hotfix and better error displays are on our list anyways and discussed in many other issues as well |
@GilgusMaximus please think about reopening since the issue is back and there is no serious fallback to utilize invidious. (which is better maintained and quicker updated, no offense) |
When I try to watch e.g.:
https://youtu.be/bvybMVRaND0
or
https://youtu.be/SlldJetZwcQ
I get the following three messages:
"Local API Error (Click to copy): Error: Status code: 404"
"Falling back to invidious API"
"Invidious API Error (Click to copy): {"error":"Could not extract video info. Instance is likely blocked."}"
(and no video)
I couldn't find another report of this problem, but if one exists, point me to it and close this.
This is on Debian 10, fully upgraded.
I just upgraded the freetube client to version 0.13.1 (over 0.11.3) from https://freetubeapp.io/#download (the x86 debian package) and succesfully reproduced this behaviour.
The text was updated successfully, but these errors were encountered: