[Bug]: Videos still not playing on v0.22.1 #6385
Comments
|
That likely means that most Mullvad servers have been flagged by YouTube, in that case you'll either have to keep searching for a server that isn't blocked or try a different VPN provider. Additionally when you say it works in your browser, is that in an incognito window while being logged out of YouTube? |
Nope, a tab that's logged in, which is an oversight on my end considering the error message literally says logging in will fix it, lol. When I just tried it in incognito, youtube allowed me to access videos seemingly regardless of server, though I admittedly only tested a handful, not as extensively as when I was trying to get things to work. After searching through for a while I did find a vpn server that allowed me to connect on the nightly build, but I made this post prior to that—probably should have left an update comment about that, my bad. Leaving the thread open for now in case further info is needed |
This comment has been minimized.
This comment has been minimized.
|
Wow, they're blocking mullvad now? Guess I'm not watching youtube anymore, so long. |
FWIW - based on testing with a browser - it's not an outright block, it's a "redirect to the tracking service known as reCAPTCHA v3". They're trying to deanonymize mullvad users via reCAPTCHA or forcing us to sign in. |
|
It is not just mullvad, I'm using proton and getting [BAD_HTTP_STATUS: 403] Potential causes: IP block or streaming URL deciphering failed. |
|
Unfortunately it's a cat and mouse game between YouTube and the people that they actually want to block (the people making too many requests and downloading too much, so as the companies that are mass-downloading videos to train their machine learning algorithms). You are just getting caught in the crossfire as you are using the same VPN IP addresses as them. |
|
Switching the VPN 2 times helped. It seems specific instances are IP blocked. |
|
Hello I'm not using VPN and seems like I'm getting hit too 9046edc - Build 5322 |
|
I'm NOT using a VPN, and I also got this error message: [BAD_HTTP_STATUS: 403] Potential causes: IP block or streaming URL deciphering failed How do I get around this? Happens on: |
|
I get this issue is caused by the use of a blocked network in my case. However, I've no issue when playing the videos from inv.nadeko.net or yewtu.be. Why this doesn't work ? I even can't load the subscription videos when selecting invidious backends. |
|
@Astaoth That's because the instances on the public Invidious instances list had turned off API support (check the API column on https://api.invidious.io), that means you can still use them if you visit their own websites directly but can no longer use them through 3rd party tools like FreeTube. Edit: looks like it's back again now, was gone for the last few days. |
This comment has been minimized.
This comment has been minimized.
|
We are looking into it, NewPipe and ReVanced seem to be affected too. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Oh I see, thanks ! I'll keep the api link in mind the next time this issue happens.
About Mullvad, they have few different providers. Maybe the issues are only with some of them and not the others ? I've already seen this with twitch and ProtonVPN, when the traffic is from 31173 (I think it's owned by Mullvad, it's also used by Proton and Nord) there are more traffic restrictions that from others. |
Can confirm. Used a server I'm not usually comfortable with for my own reasons and it worked - if anyone's in a similar boat and doesn't want to compromise on their server choices for other activities, you can use the wireguard socks5 multihop to make it so only FreeTube is coming out. My FreeTube is currently in Manchester, UK, gb-mnc-wg-005 and working while everything else is in Sweden where I like it. Edit: I didn't do extensive testing so don't take this as gospel, but the ones I tested that were owned by Mullvad failed, the ones they rented from a third party server provider worked. |
|
A wild guess but it might have something to do with secure DNS over https (default being cloudflare). For people without VPN - the cloudflare servers might be unfairly targeted. Check your browser settings for testing if you want to. |
|
I've noticed that this usually only happens to me when starting the app, and that changing the vpn to another server usually solves it, even if the new server at other times also has this problem. I wonder, could it be that retrieving many feeds with the default method (not rss), is triggering the restrictions? |
That looks like a killswitch issue on your VPN configuration. When switching from a server to an other, without killswitch, you will make a direct internet access. |
|
@Astaoth You misunderstood me entirely 🙃 I was not referring to the lapse during the server change (my mullvad killswitch works fine), but to being on another server. Regarding the point, I wonder if feed retrieval implies “this suspicious ip has made too many requests in a short time”, enough to trigger viewing restrictions; also if rss avoids it. |
efb4f5ff-1298-471a-8973-3d47447115dc
changed the title
What else can they do? This is a YouTube server issue, for us VPN users. They're IP blocking our VPNs. Even if they coded in the ability to respond to the captcha that deanonymizes us too worst case, and "best" case wastes our time training Google's """AI""" with a system that doesn't even stop bots. |
Most don't mind training the AI, and it's better that users can choose to de-anonymize or not (I understand only for that session), than to use the app or not. |
|
The only way to watch videos on a blocked IP address is to use a YouTube account on the official YouTube website or mobile apps (even the official apps and website are broken if you are not logged in, this is not a FreeTube specific problem). As mentioned in many places before FreeTube's primary goal is privacy so we definitely won't be adding support for YouTube accounts. So either look for a VPN server that isn't blocked, turn your VPN off or use the official YouTube website with a YouTube account. |
If you're willing to de-anonymize at all then you're willing to use your browser to watch YouTube whenever FreeTube doesn't work. As absidue just said, they're not going to enable you to circumvent their primary goal for the software, at that point you shouldn't be using it. That's just the lot we have. Edit: Also, reminder, earlier on in this thread I posted a working solution for Mullvad users. Sure it involves a bit of whack-a-mole but it does work, it does allow us to get around these blocks without sacrificing our regular browsing. If you're willing to jump through all the other hoops you just said, you're willing to use proxies too, so, do it. And if you're on another provider, ask them to enable that, or find a free third party proxy you can use. Like? This isn't the FreeTube dev's responsibility demanding excess work to fix a problem that their app isn't causing is a lot. At best this is a feature request, not a bug. Second edit: If you're willing to de-anonymize you can just use split-tunneling. I'm not trying to be funny, but this is a VPN issue, not a FreeTube issue. Our solutions must come from our VPN providers, and - at least mullvad - already has several. |
Ofc they can't bypass strict IP blocks, but there a few workarounds : rate-limiting the users (on certain VPN servers I only get banned after watching a few videos), caching subscriptions videos (AFAIK there is no permanent IP ban, so the app should try and fetch videos once in a while), and maybe try ipv6? |
|
OP chiming in one last time to say that turning on multi-hop in your VPN settings and turning off automatic subscription feed refresh seems to fix the issue. They seem to less so be IP blocks, and more IP time-outs, so to speak. Multi-hop and only fetching feed when requested lowers how often an individual IP you're using pings youtube, which so far has prevented me from getting a time-out again. Of course, it's possible I've just gotten lucky, but I'd recommend trying. Multi-hop should be found somewhere in your VPN settings (for Mullvad it's right there when you click the gear symbol), and disabling feed auto-fetching can be done in freetube's settings, it's the first option under the "subscription" tab. |
I can confirm that Multi-hop seems to fix the issue. I am not sure whether it's multi-hop, or just Mullvad refreshing IPs more frequently, but I haven't had VPNs blocks in a long time. And yes, time outs are an issue, so you better not watch videos for two seconds and quit. Sorry for before, Indeed, FreeTube can't really do anything about VPN blocks |
Have never used a VPN. Not a heavy user either. Still getting Local API Error (And, Invidious API Error) on latest development builds. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
If you are using 0.22.1 and are experiencing problems please DO NOT COMMENT ANYMORE, repeating things that everyone else has already said and that we have already acknowledged as a problem, is very unhelpful as it makes it a lot harder to keep track of the useful comments (people saying they are experiencing issues with the latest development changes). |
|
@OothecaPickle Your comment seems to have vanished but you mentioned that it broke temporarily for you on the nightlies, but then started working again, did it break again anytime since then? |
This comment has been minimized.
This comment has been minimized.
Mullvad allows you to multihop with a SOCKS5 Proxy, which allows you to split-tunnel in such a way where both things are still going through the VPN but coming out of different exit nodes, so you can find a server that is less likely to get blocked/isn't currently being blocked and use its SOCKS5 settings in FreeTube. |
Haven't experienced the error again, will update if I do. |
This comment has been minimized.
This comment has been minimized.
|
Doing the Mullvad Proxy stuff (https://mullvad.net/en/help/socks5-proxy) under settings -> proxy and enabling Fetch Feeds from RSS and disabling Fetch Feeds Automatically under settings -> subscriptions fixed it for me |
|
Freetube v0.22.1 Beta Flatpak Install |
|
I was not using a VPN and I had the same issue. It turns out that after I downloaded 30-ish videos using |
This comment has been minimized.
This comment has been minimized.
|
Appears changing resolution in the settings to 720p works on my end. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Maybe this issue should be reopened, so people see it's being worked on and don't post duplicate issues? Seems to be much more widespread for the last few days... |
|
It's already pinned at the top of the issue list, it doesn't get more discoverable than that. Unlike other problems in the past people have been surprisingly well behaved this time, duplicate issues have been less of a problem, more just duplicate comments (people some how think that repeating that they are experiencing it on 0.22.1 when everyone else has already, said it and we have already acknowledged it and provided a potential fix, is going to have any effect other than just being annoying). Ideally we would lock the issue to prevent the spam, but we still want to hear from the people that claim they are still experiencing problems on the latest nightly, as those comments are actually useful. |
and others
Guidelines
Describe the bug
Any video clicked on still gives both local and invidious api error, followed by either an entirely blank page or an error message over the thumbnail in the player saying "watch session expired, please log in" (paraphrasing).
Expected Behavior
Videos should play as normal.
Issue Labels
feature stopped working
FreeTube Version
v0.22.1
Operating System Version
Windows 11 Home 23H2
Installation Method
.exe
Primary API used
Local API
Last Known Working FreeTube Version (If Any)
No response
Additional Information
In the last version, this was only happening to videos which contentid flagged. now it's happening to all videos, including ones that worked on previous editions. I've tried both the .exe and the .zip installation methods. I have not tried fully deleting freetube and using a fresh install. Windows Defender and the like have been disabled on my system, so I don't think it's them interfering and damaging/corrupting files either. When testing the nightly build, it instead gave an IP blocked warning, and only allowed me to watch videos once my VPN was disabled. Disabling VPN on the main version did not seem to have any effect. It's not a specific server either, it was any time my VPN was enabled at all regardless of location, and this same bug does not occur when pulling up youtube in browser, nor with any other websites or applications. If it helps any, I'm specifically using Mullvad VPN.
Nightly Build
The text was updated successfully, but these errors were encountered: