-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Stop ignoring "HTTP Error 429: Too Many Requests" bug reports [discussion] #21729
Comments
Hi i have the same issue, also put a "new issue" but i have been marked as "duplicated". Could someone help us? |
Again: Youtube ban entire IPv6 blocks. You don't even need to ever run youtube-dl to get your "fresh" IP banned. It does not detect youtube-dl, if you run browser you'll get the same 429. |
Ok, i don't have clear the solution. Please help me. |
@dstftw I appreciate the mention of "IPv6." I wasn't aware of this being the cause of the problem before. Specifying |
Really? i cant fix my problem :( still the same error. I will try to connect via VCN and open a webbrowser hoping appear the "are you a robot" captcha... :( |
Maybe try disabling all IPv6 connectivity to your device? |
How can i do that? (i am using ubuntu btw) |
Google it?
…On Wed, Jul 10, 2019 at 8:39 PM Juan ***@***.***> wrote:
How can i do that? (i am using ubuntu btw)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21729?email_source=notifications&email_token=ADSL3QYSWQITTFGLCFDUOQ3P63IQXA5CNFSM4IAU43XKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZVVLTA#issuecomment-510350796>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADSL3Q7LESDG6SC5UAWN5QDP63IQXANCNFSM4IAU43XA>
.
|
HAHA ok thnks |
This was the piece of critical information missing from most (if not all) "bug" reports:
|
This is not a solution. I have ipv6 disabled on my server, but I still get this error. It appeared relatively recently. There are options? |
There is no special black magic. You either use not banned outgoing IP (be it your direct network interface, proxy, VPN or whatever) or it will not work. |
Hi @LyoSU Have you resolved? Please help. I don't understand how to solve it. |
I tried to use a proxy and it helped me. Looks like you just need to change the server. |
@LyoSU THanks for your replied. Ok i will try something like Proxy or change server. |
Hi! if someone needs. My Problem has been "fixed". I only stop to do "requests" to youtube with YouTube-dl, perhaps for 10 to 16 hours. And now it's working fine. |
@zapetin52 This is not a fix. I have the same and after a couple of dozen requests are blocked again. |
Ok i unterstand it's not a fix, but for me it's working again. If youtube will block me in the future i will use another IP or a Proxy. I think i will change the IP ( i don't know ) |
Here is my tries:
YouTube changed something yesterday that automatically blocks requests from youtube-dl depending on the situation. -> I agree. |
My "solution" was paid for another IP. Hoping working for a long long time. Thanks for the support |
YouTube changed something yesterday that automatically blocks requests from youtube-dl depending on the situation. Read about several popular sites going down: https://streamdroid.org/youtube-blocks-popular-mp3-stream-ripping-sites/
My site was affected too and I created several new servers (all with fresh IP addresses) and all of them were blocked as soon as the first request from youtube-dl hit.
This is not just "your server was blocked by YouTube, end of discussion" issue. I can't create a new server and set up the website again.
Please look into these bug reports and discover what YouTube has done to automatically detect youtube-dl. It has to be automatic because it happens the instant you attempt to download a video from a new server.
Here's my relevant error log from my latest server instance:
More information:
I later installed youtube-dl.exe on my personal Windows computer and it worked just fine. The only correlation with this bug is that all these instances were running Ubuntu Server 18.04 and using DigitalOcean as a host. I will continue testing with different hosts and other operating systems to see if that matters.
The text was updated successfully, but these errors were encountered: