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

Closed
opened 2024-10-24 20:57:39 -03:00 by Fijxu · 11 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
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.
Author
Owner

wtf google Blocked the external proxies of Backend 1 & 2 at ~00:00 UTC-3

I'll investigate later.

wtf google Blocked the external proxies of Backend 1 & 2 at ~00:00 UTC-3 I'll investigate later.

something is still wrong with those backends (not necessary with tokens). also, still not sure how we should understand/use these backends...

  • if I am in EU should I use Backend4 as this should be the best latency-wise for me? (this scenario not working for me)
  • or should I use Backend4 only for videos that were uploaded from EU? (this scenario partially works for me 30% of times)

are those backends for us or for the videos? either way, something is wrong down the line.

for example, yesterday I was able to watch all native videos from https://inv.nadeko.net/feed/trending?type=Music&region=HK only on Backend1. the rest of backends did not work at all - and yes, I checked every native video against all backends one by one.

in same fashion, all native videos from https://inv.nadeko.net/feed/trending?type=Music&region=KR worked only on Backend2

today (I tried like 120+ videos) the only working backend is 3 (with serious buffering issues - my preferred video quality is set on HD720, but picture is blocky like 360p which is sad considering my decent speeds)

and of course there are videos that cant be played on neither backend (The media could not be loaded, either because the server or network failed or because the format is not supported.) for example, I'm trying to play https://inv.nadeko.net/watch?v=AdTX0Ff8IFc for over 40 minutes rolling and shifting over all backends and still can't play it.

atm, does every (registered) unique user, have a unique token for every unique backend?

something is still wrong with those backends (not necessary with tokens). also, still not sure how we should understand/use these backends... - if I am in EU should I use Backend4 as this should be the best latency-wise for me? (this scenario not working for me) - or should I use Backend4 only for videos that were uploaded from EU? (this scenario partially works for me 30% of times) are those backends for us or for the videos? either way, something is wrong down the line. for example, yesterday I was able to watch all native videos from https://inv.nadeko.net/feed/trending?type=Music&region=HK only on Backend1. the rest of backends did not work at all - and yes, I checked every native video against all backends one by one. in same fashion, all native videos from https://inv.nadeko.net/feed/trending?type=Music&region=KR worked only on Backend2 today (I tried like 120+ videos) the only working backend is 3 (with serious buffering issues - my preferred video quality is set on HD720, but picture is blocky like [360p](![image](/attachments/47fcc26e-e208-4885-9250-764eb3858a6a)) which is sad considering my decent [speeds](![image](/attachments/fe147738-b770-4a2b-9c4a-7a726bf0e4c4))) and of course there are videos that cant be played on neither backend (The media could not be loaded, either because the server or network failed or because the format is not supported.) for example, I'm trying to play https://inv.nadeko.net/watch?v=AdTX0Ff8IFc for over 40 minutes rolling and shifting over all backends and still can't play it. atm, does every (registered) unique user, have a unique token for every unique backend?
Author
Owner

still not sure how we should understand/use these backends...

Yeah I should explain in a wiki page what is the difference between them. The difference between then is:

  • The IP address from where the backend gathers the data from youtube
  • and the location of the external proxy

All backends on the Invidious side use IPs from south america (VPN or my own IP) but each backend uses their own external proxy hosted on other countries like USA or Germany; Why? Because of bandwidth. I need to spread the load across servers or my instance would explode.

atm, does every (registered) unique user, have a unique token for every unique backend?

No, no user has a unique tokens, everyone is using the server side random generated tokens that are unique per backend.

About the videos from a specific region, I have no idea what is happening there.

>still not sure how we should understand/use these backends... Yeah I should explain in a wiki page what is the difference between them. The difference between then is: - The IP address from where the backend gathers the data from youtube - and the location of the external proxy All backends on the Invidious side use IPs from south america (VPN or my own IP) but each backend uses their own external proxy hosted on other countries like USA or Germany; Why? Because of bandwidth. I need to spread the load across servers or my instance would explode. >atm, does every (registered) unique user, have a unique token for every unique backend? No, no user has a unique tokens, everyone is using the server side random generated tokens that are unique per backend. About the videos from a specific region, I have no idea what is happening there.

About the videos from a specific region, I have no idea what is happening there.

maybe it has something to do (partially) with Withelisted and Blacklisted regions (?), as sometimes I encounter such videos

image

like for example, if video is Blacklisted in US and backend uses US IP to access it? dunno...

this I can play on Backends 1,2,4 but not on Backend 3. question is, is it because of my location or backend itself... or maybe all videos have B/W regions (and its a hidden attribute), but it's not always shown.

> About the videos from a specific region, I have no idea what is happening there. maybe it has something to do (partially) with Withelisted and Blacklisted regions (?), as sometimes I encounter such videos ![image](/attachments/048d415d-05f1-47f6-8c72-b59e13ca0bf3) like for example, if video is Blacklisted in US and backend uses US IP to access it? dunno... [this](https://inv.nadeko.net/watch?v=R_clisSImS4) I can play on Backends 1,2,4 but not on Backend 3. question is, is it because of my location or backend itself... or maybe all videos have B/W regions (and its a hidden attribute), but it's not always shown.
Fijxu pinned this 2024-10-28 16:36:50 -03:00

all backends are dead:

all backends are dead:
Author
Owner

Everything is working fine and I have received no complaints in the last 2 weeks sooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo

Everything is working fine and I have received no complaints in the last 2 weeks sooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Fijxu closed this issue 2024-11-07 23:14:53 -03:00
Fijxu unpinned this 2024-11-16 11:38:19 -03:00
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.