Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Error] This content isn't available #131

Open
BrightDV opened this issue Feb 24, 2024 · 6 comments · Fixed by #137 · May be fixed by #153
Open

[Error] This content isn't available #131

BrightDV opened this issue Feb 24, 2024 · 6 comments · Fixed by #137 · May be fixed by #153
Labels
bug Something isn't working

Comments

@BrightDV
Copy link

BrightDV commented Feb 24, 2024

Describe what happened

Video playback does not work.

Instance URL

https://tube.kuylar.dev

LightTube & InnerTube versions

v2024.2.20 / ?

Resource path

https://tube.kuylar.dev/watch?v=h04_4Msuw2k

Language & region

fr_FR

Stack trace

None, returns a 200.

Notes

This issue happened to invidious too, see this issue.
YouTube may have started to block your instance :/
The video plays fine on these instances, however:

image

@BrightDV BrightDV added the bug Something isn't working label Feb 24, 2024
@kuylar
Copy link
Member

kuylar commented Feb 24, 2024

Looks like a YouTube block, fixed in tube.kuylar.dev

For the instance hosters in future: check out Invidious' Smart IPv6 Rotator script

Leaving this issue up until we add a check for the video ID in YouTube's response

@BrightDV
Copy link
Author

Thanks for the fast fix!

@BrightDV
Copy link
Author

BrightDV commented Mar 30, 2024

Hello,
New blocking round from YouTube, other frontends are also blocked:
image

Your instance, LightTube v2024.3.9, url: https://tube.kuylar.dev/watch?v=UDVtMYqUAyw

Maybe useful:
NewPipe workaround (used by Invidious): TeamNewPipe/NewPipe#8713 (comment)

@kuylar
Copy link
Member

kuylar commented Mar 30, 2024

This is a different issue, but I will keep it here since both of them can be fixed with the same update.

Been working on this for the past day and I cant find a good way of beating this, as now they require a PoToken from Google Play Services (source: ReVanced/revanced-patches#2878 ). YouTube hit us very hard this time.

This leaves us to either:

  • use clientName: IOS, but that lacks a lot of adaptiveFormats (used by DASH playback, which we don't use but show in the download dialog), and most importantly, the formats field, which we need for compatibility mode, or
  • use the formats from clientName: WEB, which would be good, but unfortunately, that requires us to parse the player JavaScript from YouTube to solve 2 challenges. Since Invidious, NewPipeExtractor and yt-dlp were already doing this from the beginning, they can just fall back to the WEB client with an update. (here's yt-dlp doing it: [ie/youtube] Remove android from default clients yt-dlp/yt-dlp#9553)

I am currently working on implementing the latter, and I'd say that I'm 70% the way there (one out of two challenges solved) and the only thing that remains is now to make the playback URLs not throttle to 60-70kbps, which is where running the JavaScript comes in.

This update will take some time. In the meantime, disable compatibility mode in settings, as HLS playback isn't affected (as it uses the iOS client instead of android)

Note

unfortunately, because of #133, you'll have to paste the following into your browser's JavaScript console to turn off compatibility mode. sorry

document.cookie = "compatibility=false; path=/;"

@epman100
Copy link

Hello, New blocking round from YouTube, other frontends are also blocked:

new variants of that problem here & here

those are not affected by LightTube

@kuylar kuylar reopened this May 1, 2024
@kuylar
Copy link
Member

kuylar commented May 1, 2024

Wrong, normal formats (and also the download links) are blocked. lighttube-org/InnerTube#45 fixes this in the long term by not using the ANDROID client, but merging that to master will take some time. A fix will be up in https://tube-nightly.kuylar.dev in a week or two

@kuylar kuylar linked a pull request May 22, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants