Failed to perform an HTTP request to YouTube because of rate limiting

[satish2832]

Failed to perform an HTTP request to YouTube because of rate limiting. This error indicates that YouTube thinks there were too many requests made from this IP and considers it suspicious. To resolve this error, please wait some time and try again -or- try injecting an HttpClient that has cookies for an authenticated user.

[satish2832]

Any suggestions to overcome this issue ?

[Tyrrrz]

All of the suggestions are in the error message.

[ComputerMaster1st]

Hi There,

I have a question. Any ideas what cookies should be used? There's a lot of cookies and I'm unsure which ones we should try using to inject into the httpclient.

[Tyrrrz]

Not sure, haven't tried it myself. You can try using all of them.

[ComputerMaster1st]

https://i.gyazo.com/8b37f07d9aeaed050b1cc23df0f843d4.png << Here's a screenshot of what cookies are available to me. This is my own account though. I plan to make a separate account to test with.

I think we need to use the following cookies based on their expiry time >> https://i.gyazo.com/c61ac02547596541164fd83b73a4aec2.png

Looks like I've gotta wait for the 429 to clear before attempting the cookie test. I've tried all cookies with 429 in place and still not working. It's probably safe to say the cookies take IP into consideration and maybe other factors. I can only guess the cookies need to generated on the same system that's using the library. Otherwise it might always fail.

I'm only guessing at this point. I think we need to use the LOGIN_INFO cookie as others are either session only or for ads.

[MeteorBurn]

https://i.gyazo.com/8b37f07d9aeaed050b1cc23df0f843d4.png << Here's a screenshot of what cookies are available to me. This is my own account though. I plan to make a separate account to test with.

I think we need to use the following cookies based on their expiry time >> https://i.gyazo.com/c61ac02547596541164fd83b73a4aec2.png

Looks like I've gotta wait for the 429 to clear before attempting the cookie test. I've tried all cookies with 429 in place and still not working. It's probably safe to say the cookies take IP into consideration and maybe other factors. I can only guess the cookies need to generated on the same system that's using the library. Otherwise it might always fail.

I'm only guessing at this point. I think we need to use the LOGIN_INFO cookie as others are either session only or for ads.

You need:
YSC; PREF; VISITOR_INFO; SID; HSID; SSID; APISID; SAPISID; LOGIN_INFO

100% work

PREF is optional cookie, but it set language of YouTube interface

[satish2832]

How to get the extract of cookies in run time from youtube

[ComputerMaster1st]

https://i.gyazo.com/8b37f07d9aeaed050b1cc23df0f843d4.png << Here's a screenshot of what cookies are available to me. This is my own account though. I plan to make a separate account to test with.
I think we need to use the following cookies based on their expiry time >> https://i.gyazo.com/c61ac02547596541164fd83b73a4aec2.png
Looks like I've gotta wait for the 429 to clear before attempting the cookie test. I've tried all cookies with 429 in place and still not working. It's probably safe to say the cookies take IP into consideration and maybe other factors. I can only guess the cookies need to generated on the same system that's using the library. Otherwise it might always fail.
I'm only guessing at this point. I think we need to use the LOGIN_INFO cookie as others are either session only or for ads.

You need:
YSC; PREF; VISITOR_INFO; SID; HSID; SSID; APISID; SAPISID; LOGIN_INFO

100% work

PREF is optional cookie, but it set language of YouTube interface

May I ask what you did to determine this please? What was your testing method and how often did you do these tests?

How to get the extract of cookies in run time from youtube

Use your browser's built-in developer tools. Googling about it can help.

[Tyrrrz]

Seems like the question was answered.

[ComputerMaster1st]

Hi There,

Okay, now I received 429 with cookies. It's possible YouTube tracks user activity/history to make sure users aren't botting on logged accounts. I'm guessing we have to use accounts we actively use ourselves to perhaps avoid it as using cookies has worked for a while. I can only guess that a few cookies might need to be kept updated or something.

I'm unsure at this point.

TL;DR: There is no solution to get past the 429 other than paying for so many IPs and rotate through them somehow which involves breaking the httpclient or maybe recreate it all the time.

[duckieu1989]

Failed to perform an HTTP request to YouTube because of rate limiting.\r\nThis error indicates that YouTube thinks there were too many requests made from this IP and considers it suspicious.\r\nTo resolve this error, please wait some time and try again -or- try injecting an HttpClient that has cookies for an authenticated user.\r\nUnfortunately, there's nothing the library can do to work around this error.

[tinazhe]

Failed to perform an HTTP request to YouTube because of rate limiting.\r\nThis error indicates that YouTube thinks there were too many requests made from this IP and considers it suspicious.\r\nTo resolve this error, please wait some time and try again -or- try injecting an HttpClient that has cookies for an authenticated user.\r\nUnfortunately, there's nothing the library can do to work around this error.

did you find a solution to this?

[duckieu1989]

Hi Tyrrrz, I wite log ex detail i see log :Hosting IP band by Youtube. I buy new hosting and deploy it okie :) Vào CN, 1 thg 11, 2020 lúc 15:55 Tinashe Dube <notifications@github.com> đã viết:

Failed to perform an HTTP request to YouTube because of rate limiting.\r\nThis error indicates that YouTube thinks there were too many requests made from this IP and considers it suspicious.\r\nTo resolve this error, please wait some time and try again -or- try injecting an HttpClient that has cookies for an authenticated user.\r\nUnfortunately, there's nothing the library can do to work around this error. did you find a solution to this? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#376 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIMZCLPJP5546AFKHNJ4GJLSNUO6TANCNFSM4M5Q46IQ> .

-- Kiều Trọng Đức Skype: duckt1989 Email: duckt1989@gmail.com Phone: 091.55.44.33