[Bug] Youtube seems to block tokens if they aren't from the same country (Just a Theory) #26

Open
opened 2024-10-24 20:57:39 -03:00 by Fijxu · 5 comments
Owner

image

I tried to watch a video using my tokens but the /videoplayback request returns error 403. I deleted the tokens from my account and now every video works on every backend. Not sure what is happening here.

Fix? Idk I don't have time to fix it now.

Maybe you can't use the same token for the same video but on a different backend?

Maybe the IPs that I use for external proxies got blocked? If yes, that would be pretty bad.

No fucking idea kms

![image](/attachments/951f5cd4-ed9f-461a-9d6b-9be0a1ad8d64) I tried to watch a video using my tokens but the `/videoplayback` request returns error 403. I deleted the tokens from my account and now every video works on every backend. Not sure what is happening here. Fix? Idk I don't have time to fix it now. Maybe you can't use the same token for the same video but on a different backend? Maybe the IPs that I use for external proxies got blocked? If yes, that would be pretty bad. No fucking idea kms
128 KiB
Fijxu commented 2024-10-24 21:15:18 -03:00
Author
Owner

yeah the IP got fucking blocked or some shit fucking shit google. I'll fix it tomorrow.

If invidious is slow it's because of the lack of bandwidth. Too many people is using it since it's the only one alive lol!

Also try https://invidious.catspeed.cc. Spread the load across instances!!!!!

yeah the IP got fucking blocked or some shit fucking shit google. I'll fix it tomorrow. If invidious is slow it's because of the lack of bandwidth. Too many people is using it since it's the only one alive lol! Also try https://invidious.catspeed.cc. Spread the load across instances!!!!!

image

yes it did happen. its like that since you fixed it with token generation. feels like some regional block or something. what works on one backend often cant be reproduced on another backend.

most of the time I find myself switching between backends as I watch american vs asian stuff

maybe we need one token per each backend instead of one token per all 4 backends? dunno, just an uneducated guess.

![image](/attachments/52f59578-2d79-4ae2-9ab9-451760eeb2eb) yes it did happen. its like that since you fixed it with token generation. feels like some regional block or something. what works on one backend often cant be reproduced on another backend. most of the time I find myself switching between backends as I watch american vs asian stuff maybe we need one token per each backend instead of one token per all 4 backends? dunno, just an uneducated guess.
Author
Owner

Why no one told me (;゚Д゚)

Why no one told me (;゚Д゚)
Author
Owner

Token generation has been disabled. Everyone will be using the auto generated server tokens for now.

Token generation has been disabled. Everyone will be using the auto generated server tokens for now.
Author
Owner

maybe we need one token per each backend instead of one token per all 4 backends? dunno, just an uneducated guess.

I already do that btw. Each backend has their own token.

>maybe we need one token per each backend instead of one token per all 4 backends? dunno, just an uneducated guess. I already do that btw. Each backend has their own token.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Fijxu/invidious#26
No description provided.