-
-
Notifications
You must be signed in to change notification settings - Fork 29
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] YouTube sign In Bot Protection #335
Comments
So it appears, also adding |
Guess I was wrong, still failing. Shortly after my last comment the log started being filled with
|
Looking at the log I am thinking this maybe a rate limiting thing from downloading too many videos too quickly. It fails on several (5-10 usually) then gets 1 successfully. |
|
Thank you for reporting this! This is a known issue with yt-dlp: yt-dlp/yt-dlp#10128, I forgot to mention it in this repo. Unfortunately it looks like there is little to do, Youtube is becoming more aggressive with banning IPs which look illegitimate from their PoV. The ban can be temporary or permanent. And it looks like it is based on IP history + ASN, i.e. if you run the scraper from a residential IP you have less chances to be blocked than when you run it from a server on a hosting provider. But risking banning your own residential IP is probably not something you want to consider, might cause some trouble at home ^^ |
No worries. I am thinking some logic change may be a way to get around this. Something like (obviously not working code, because it is not for a specific language but more of a flowchart idea).
|
I don't think the problem happens only when type is |
I cloned the repo and did a docker build of the image. I then ran the following command to try and get an entire channel on YouTube
Every single video it tries to grab logs a message like this
I am not sure if it is something I am doing, or if the YouTube Bot protection has essentially broken this tool. Looking at the help for youtube2zim I do not see a way to specify youtube login credentials, and I would assume the API key would work fine once the
YouTube Data API v3
has been added to it. Is there more I need to add to my API key to make this work?The text was updated successfully, but these errors were encountered: