-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
404 error on version 1.9.10 #144
Comments
same issue, since yesterday |
Seems youtube removed (again) the Note that it won't be possibile to extract age-restricted videos at all now |
That's quite a sizeable amount of videos now inaccessible. May I know the cause of the limitation preventing age-restricted videos from being extracted? I probably won't understand but I'd like to be aware. Is this a temporary sticking point or is this change something that can't be worked around? Edit: Found and read #141. |
@lrorpilla Before YouTube patched this out, there was a way to extract age-limited videos(which usually require to be logged in) using some sort of workarounds. But now there is no way to access those videos anymore, the only solution would be to pass the cookies of a logged in user |
Thing are working for me now, thanks for the quick fix! I used to work for a company that did web scraping of bank websites and we had to do all kinds of things to get around the anti-bot measures those banks put in place, often powered by Akamai. It was definitely a last resort since it required a lot more processing power for the bulk scraping we were doing, but when nothing else worked we could usually outsmart the bots by using Puppeteer. Not sure if it would be worth looking into that as a way to get around the age-limited video block. It might, at least, provide an easy way to get a hold of a logged in user's cookies for the rest of the requests. |
I'm getting the same error as described in this issue that was marked fixed a month ago in version 1.9.5, but I'm experiencing the issue in version 1.9.10 no matter what videoId I use. The error is as follows:
An example of the call I'm trying to make:
The text was updated successfully, but these errors were encountered: