-
Notifications
You must be signed in to change notification settings - Fork 51
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
Block detected on certain videos #1662
Comments
I have similar issues. I noticed that when I'm on wifi it immediately triggers the "block detected", but on mobile data I can usually get the forst chunk of the video to play and then it triggers block detected around 1 minute and enters reset loop |
Getting this, but differently. The first video might load fine but everything after that gets a block detected attempting bypass error on the 1:00 minute mark for all videos, even the ones that played just fine. It fixes itself after some time but breaks after a couple videos. I can't tell how long it takes for it to work again, but its not something that fixes itself on app restart. |
Adding some more information here. This ONLY happens when I am connected to a VPN, regardless of VPN settings or GrayJay settings. I have also tried activating the "Force Experimental UMP Streams" setting, but that seems to cause other issues no matter whether I use the VPN or not (still unable to play YouTube videos that is). Curiously I reside in Sweden and use Mullvad VPN (based in Sweden) and am connected to a server which is also in Sweden. I have tried enabling and disabling certain VPN settings (Multihop, DAITA [with and without Direct Hop] and DNS content blockers) but none seems to make a difference. Simply being connected to a VPN seems to cause videos to not play for more than 59 seconds. |
I experience the same issue with videos stopping exactly at 1.00 mins after I have watched the first. Today I managed to watch some kind of live stream for several hours, so I thought it was ok again... But now same problem occurs- cant connect to channel or something, is the error message. I know I don't sound especially competent but Ive used Grayjay several hours daily for a long period, but never earlier have I experienced a problem I couldn't fix only using logic, basic knowledge and tips like switching on/off ' and of course reading relevant info provided when installing directly from the source (not Play)... |
This occurs for me also (when my vpn is on), but I thought it worth noting that the behavior does not occur on the new Grayjay Desktop application, even with the same vpn enabled. Perhaps the desktop app is doing something different, which would be worth looking into. |
That is interesting, for Grayjay Desktop I can still only play 1 minute with my VPN Connected. Interestingly I could not use Split Tunneling to accept the GrayJay executable to bypass the VPN, this just made anything refuse to load, even thumbnails. Unsure why that happens. I do believe my initial comment should have maybe been put on #1610 instead however as this seems more relevant. |
On desktop I get the following error Reloading doesn't fix the problem, because it still stops the video from loading beyond the first minute. On mobile I get
and
After that I cannot watch for more than one minute again. All of these findings are the same both with and without mullvad VPN on |
Got this crash, this time it was on the 47th second
|
@JordyScript, I get the same thing on GrayJay Desktop, I opened an issue on the Desktop repo: futo-org/Grayjay.Desktop#258 |
What happened?
On certain videos, constantly getting:
Using IOS sources fallback (cached) -> Block detected attempting fallback -> Media Error The media source encountered an unauthorized error...
Tried reinstalling the plugin, but it did not help. Fidgeted with the plugin options also, no change (Youtube activity, logout, etc.).
Android 14
Grayjay Version
278
What plugins are you seeing the problem on?
Youtube
Plugin Version
219
When do you experience the issue?
Are you using a VPN?
No
Relevant log output
51085fbe-7532-4086-b823-978cb47a3a23
The text was updated successfully, but these errors were encountered: