[Bug] Content not available in this app. upgrade to latest version of youtube.

[accessiblepixel]

Continuation of #3217 as it was closed so that I couldn't reopen.

Getting same message again, and this time have tried in multiple browsers with no extensions, after cleaning cache, disabling extensions, enabling extensions on my own invidious install in docker on linux from latest tag.

Obviously something isn't working right, even in a fresh browser with no extensions.

I'm trying to report again. Tell me what you need to debug it, as didn't feel it was looked at properly last time.

[unixfox]

Please post the video(s) ID that you tested.

Also for these video ID please check if you can reproduce the same issue on others public instances: https://instances.invidious.io/

[accessiblepixel]

Also something from this list makes it work for a video again.: refreshing, viewing different videos, turning proxy on/off, restarting docker...

It's an intermittent thing, and doesn't seem to be dependent on a specific video, but once it rears it's head, it won't show on the instance in any browser.

The two videos in the last thread did, and the videos will work fine on a public instance, because it's something intermittent going wrong with the core.

[unixfox]

In which country is your invidious instance located?

So do you confirm that you have no issues whatsoever on most of the public instances and that you are currently only able to reproduce this issue on your local invidious installation?

[accessiblepixel]

I've tested the couple of videos I've found that don't work on a public installation and the videos that haven't worked for me have worked on public instances. After fiddling for a while with it, something in the above list, it will start working again, but so far I haven't figured out what fixed it. Updating fixed it last time because it wipes anything that might be cached and restarts it so...

I don't use public instances enough to see if the problem rears it's head or not, I've only used public instances to check to the videos that haven't worked.... although this time when one video stopped, they all stopped and started showing that 5 minute video again.

It's hosted in the UK on my internet connection. In docker on a VM running Debian Linux 11 (bullseye), on top of the Proxmox hypervisor.

[unixfox]

@SamantazFox any ideas about this issue?

On matrix people were talking about the fact that we are using an old version of the ANDROID client: https://github.com/iv-org/invidious/blob/master/src/invidious/yt_backend/youtube_api.cr#L46

[SamantazFox]

yeah, that could be related to the client version. I need to bump them ^^

[coletdjnz]

TeamNewPipe/NewPipe#8713 (comment)

[accessiblepixel]

Okay, I've done a little digging, but it's so intermittent it's hard to get good debug data.

I'm not exactly sure what I'm looking for, but in web developer network console, when the video shows the error message, when it's trying to start playback it gets a HTTP 200 straight away then that video loads.

On videos where it works normally I get a 302 Moved, then it goes to a HTTP 200.

What do I need to be on the lookout for in the network tab, since there's a lot of stuff happening here and I'm not familiar with much of it (I just use invidious and know my away around some web development).

[unixfox]

What do I need to be on the lookout for in the network tab, since there's a lot of stuff happening here and I'm not familiar with much of it (I just use invidious and know my away around some web development).

It's not directly related to invidious, it's an issue between invidious and youtube servers. You won't see anything in the network tab as all the requests are done inside invidious.

On your side you can't do anything if you don't have some background in reverse engineering, you will have to wait that the community find a solution for this issue.

[unixfox]

@accessiblepixel Can you me help me with these questions:

• Do you sometimes use the official YouTube app on your internet? On your phone with YouTube for Android, or on www.youtube.com with your computer?
• Do you have IPv6? You can find out if you have it here: https://ipv6test.google.com or https://test-ipv6.com
• Can you give the IP address that you get for the domain www.youtube.com when the error appears. On Windows and Linux, you can find it through the command line/terminal by entering nslookup www.youtube.com
• Do you have this error after viewing a few videos, or it appears straight away on the first video that you watch for the day?

These questions will help us replicate this issue on our side because it's very tricky to replace the error, I haven't been able to do it even after 300 tries of loading the same video.

[accessiblepixel]

@unixfox

Yes, my partner uses the official YouTube website on our internet (with Firefox on his computer) and I think he sometimes browses on his phone, but the error video comes up regardless of whether he's using it (I know he's not using it when he is asleep and I am not 😃)

We don't have IPv6 enabled.

The error comes a couple of times a day, usually after watching a few videos. I've taken to just not watching the video that doesn't work and move on to another one or if I really want to watch it, open it on the YouTube website.

If I can help further, please don't hesitate to ask. Next time it happens I will post the lookup for the youtube domain. :)

Kind regards,
Jessica

[unixfox]

@accessiblepixel Thanks to the collaboration in the YouTube reverse engineering community, we finally found the missing parameter (TeamNewPipe/NewPipe#8713 (comment)) that resulted in the error that you got.

Please update Invidious and the error will be fixed.

[unixfox]

We should probably add an exception if we find that the videoID returned is not the correct one, like yt-dlp did: https://github.com/yt-dlp/yt-dlp/pull/4593/files

This may allow debugging future issues quicker.

[accessiblepixel]

I've updated and I haven't yet seen the same error again.

It seems like @unixfox 's suggestion of throwing an exception if the returned video isn't the expected one would be very useful and I see they've opened #3257 for that. That would be very useful, it would have helped me not feel like I was loosing my mind :p

Thanks all.

[accessiblepixel]

I've not seen this error from #3230 since, except today where I tried to watch a video and it came up, so it looks like in certain circumstances it's still possible? Was the debug thing not added, where if the video that comes back isn't the video id requested to throw some kind of exception?

[unixfox]

A debug code is going to be added in #3278. I'm waiting for the confirmation from @SamantazFox.

I'll update you in this github issue once it has been added.

[unixfox]

@accessiblepixel Please update invidious and report any bug related to the error from this github issue.

[accessiblepixel]

Alright, I've updated to 2022.08.23-16b23ef @ master`, and will report back if/when I see the error again.

It is a lot less common with the change from #3255 though, for sure, but I've seen it a couple of times now. :)

[accessiblepixel]

Okay, yes, I got a video that doesn't appear and shows the same message and video like before today.

Let me know what info and debugging info I need to provide.

[unixfox]

You didn't get the error message like this?:

Please send us:

• The video ID of the YouTube video that have the issue
• A screenshot of the video that have the issue

[accessiblepixel]

No, I didn't get a debug error like that, unfortunately.

I missed screenshotting when it happened last time, but I will grab it when it happens again. Is the debug information available in 2022.08.23-16b23ef @ master? That's the version that I got when I updated the docker, was it added at that time?

Thanks,
Jessica

Edit: Also yeah, like last time it doesn't seem like it's tied to a particular video. One video wasn't working last night (showed that 5 minute video) but this morning it worked fine, so I'm not sure that giving a video url would definitely reproduce the issue. Of course I'll provide it to help with debugging, but yeah, still seems pretty random, but a lot less than before.

[unixfox]

Yes 2022.08.23-16b23ef @ master is the latest version available on Invidious, and it has the debug information added to it.

Even though the issue may not be related to a particular video, it's still useful information that we can use in order to diagnose the issue. The thing is that we don't know if the potential issue affect some videos or all the videos on YouTube.

By having the video ID/URL, we can be sure that either it affects all the videos or some videos.

If you happen to reproduce the issue again, sending us a screenshot would really help us.

On my side, when I have time I'll try to reproduce the issue.

[accessiblepixel]

No problem. I'll get you a screenshot when it happens again and the video URL :)

---

Here's the screenshot as promised here. and the video where it happened is watch?v=bWRFDVjb-xo

---

Another broken video here. video URL is watch?v=mepmJJ62ZFU

[unixfox]

Thank you for the screenshot and the video IDs. I'll investigate.
(by the way, please don't triple post, instead edit your last message, it helps in keeping this issue "clean". no need to reply to my message, you can add a reaction with the emoji 👀 if you want to tell me that you have seen it.)

[unixfox]

Could you set the log_level to All in the config.yml file and then restart Invidious?

When you encounter the issue again, get the logs from 5 minutes before the issue happened to the very last logs. Then upload them on https://paste.ee. It's ok if there are too many lines in the logs.

If you installed Invidious using docker-compose, you can get the logs using docker-compose logs --tail=10000. 10000 means it will show you the last 10000 lines, increase or decrease the number in order to find the corresponding lines, check the date it's normally written at each line.

And also tell us the videoID where the issue happened.

If you don't want to publicly share the logs (which I completely understand), then send us the link by email to contact [at] invidious [dot] io. (Obviously, replace the [at] and the [dot])

---

Finally no need to do anything! I was able to reproduce the issue on my end.

About the debug message in Invidious that should have been included in the latest version it wasn't properly implemented. So please update Invidious to the latest version (a7d9df5), and you will see the debug/error message now.

---

EDIT: Found the issue, it's the user agent, we are sending this one: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.97 Safari/537.36 but we should be sending this one for the ANDROID client:
com.google.android.youtube/17.10.35 (Linux; U; Android 12; GB) gzip

I've opened an issue so that we replicate more precisely the data sent by a real Youtube app on Android: #3256

[unixfox]

Hello @accessiblepixel can you try if the issue is now fully fixed.

We pushed some changes. You will need to update invidious.