Open khaouitiabdelhakim opened 6 days ago
Same here.
@khaouitiabdelhakim Were you able to find why?
Hey @elvismdev I have had a same library https://github.com/khaouitiabdelhakim/Get-YouTube-Stream-Urls-JS that uses almost the same logic but it stops working just the 5 passed days due to 403 error. I do not know why because every thing is great until the passed 5 days hhh.
But I have today found a great other way to do it, and I'm testing it on my android streaming app https://play.google.com/store/apps/details?id=com.abdelhakim.faborfy, that you can check out @elvismdev.
the idea is that youtube has many client types and version like ANDROID, WEB_REMIX ... DESKTOP and more. so I try to try the same logic of that library on all of them, it works for some videos but not for all;
You can check this method (by the way the solution I'm talking about is in Kotlin; I use it in my android Faborf app)
@elvismdev check this https://github.com/khaouitiabdelhakim/Get-YouTube-Stream-Urls-JS it is more expressive, but Until now I could not figure out the reason of 403 error Here all the possbile problems that can be a cause that I tried to use but they do not same to be the cause 1- The youtube player uses a custom player with a custom timestamp so the ciphering method got from the base.js must be compatible with the version of the player: I tried to get urls and base.js of the same version but it did not work. 2- I thought that the problem was due to the rate limit or malicious activity detected by youtube so I tried to use a vpn; request using the vpn and cipher using the same ip address but it did not work; 3- Hope someone fix it because this problem is so FRESH 4- Meanwhile @elvismdev check this out https://tyrrrz.me/blog/reverse-engineering-youtube-revisited it is so good to unserdtand how all these libraires work;
Facing same 403 error for the last few days. @khaouitiabdelhakim @elvismdev any solutions so far?
I will try to resolve this issue this weekend.
Access to rr2---sn-f5o5-jhod.googlevideo.com was deniedYou don't have authorization to view this page. HTTP ERROR 403