Originally created by @2shiraz on GitHub (Jul 9, 2024).
problem description
I host cobalt instances on my servers. I am getting my Youtube oAuth timed out/rate limited every 15 mins. After that, I have to replace it with another account token ( currently I replace it with the previously used account token ). I'm just asking here to find out if anyone else getting this too? I saw the main cobalt instances were not affected.
Rate Limited Account :
ps: I handle around 3 million user/m traffic
Originally created by @2shiraz on GitHub (Jul 9, 2024).
### problem description
I host cobalt instances on my servers. I am getting my Youtube oAuth timed out/rate limited every 15 mins. After that, I have to replace it with another account token ( currently I replace it with the previously used account token ). I'm just asking here to find out if anyone else getting this too? I saw the main cobalt instances were not affected.
Rate Limited Account :

ps: I handle around 3 million user/m traffic
if you have several youtube tokens in the cookies file, cobalt will distribute requests between all of them evenly, reducing the probability of each specific one getting rate limited
@wukko commented on GitHub (Jul 10, 2024):
if you have several youtube tokens in the cookies file, cobalt will distribute requests between all of them evenly, reducing the probability of each specific one getting rate limited
if you have several youtube tokens in the cookies file, cobalt will distribute requests between all of them evenly, reducing the probability of each specific one getting rate limited
Yes, just figured it out. Didn't know that the rotation algorithm was there till I checked the code. Thanks anyways, saved my day literally!
@2shiraz commented on GitHub (Jul 10, 2024):
> if you have several youtube tokens in the cookies file, cobalt will distribute requests between all of them evenly, reducing the probability of each specific one getting rate limited
Yes, just figured it out. Didn't know that the rotation algorithm was there till I checked the code. Thanks anyways, saved my day literally!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @2shiraz on GitHub (Jul 9, 2024).
problem description
I host cobalt instances on my servers. I am getting my Youtube oAuth timed out/rate limited every 15 mins. After that, I have to replace it with another account token ( currently I replace it with the previously used account token ). I'm just asking here to find out if anyone else getting this too? I saw the main cobalt instances were not affected.
Rate Limited Account :
ps: I handle around 3 million user/m traffic
@devilr33f commented on GitHub (Jul 9, 2024):
you can use multiple youtube accounts and it'll help you to hit the youtube limits less
@wukko commented on GitHub (Jul 10, 2024):
if you have several youtube tokens in the cookies file, cobalt will distribute requests between all of them evenly, reducing the probability of each specific one getting rate limited
@2shiraz commented on GitHub (Jul 10, 2024):
Yes, just figured it out. Didn't know that the rotation algorithm was there till I checked the code. Thanks anyways, saved my day literally!