[Bug] Says IP blocked but NewPipe works

[Kobaxidze256]

Checklist (Your issue will be automatically closed if you delete this part)

• I make sure that there are no existing issues - open or closed - which I could contribute my information to.
• I understand that issues with limited impact, such as those occurring on specific devices or under specific network conditions, will not be fixed.
• I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
• I have attached the error report in the issue.

Describe the bug
I haven't been able to play a lot of videos over home wifi for i think a month now. They never start playing.

Frequency
Only certain videos.

Steps to reproduce the bug
Try playing https://www.youtube.com/watch?v=-jRKsiAOAA8 or other specific video on home wifi.

Device (e.g. Pixel 9 Pro)
Xiaomi Redmi 8 running Lineage OS

Error report

Exception

• User Action: play stream
• Request: Player error[type=ERROR_CODE_IO_UNSPECIFIED] occurred while playing https://www.youtube.com/watch?v=-jRKsiAOAA8
• Content Country: GE
• Content Language: ka-GE
• App Language: ka_GE
• Service: YouTube (Anonymous)
• Version: 4.2.1
• OS: Linux Android 14 - 34

Crash log

com.google.android.exoplayer2.ExoPlaybackException: Source error
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleIoException(ExoPlayerImplInternal.java:641)
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:617)
	at android.os.Handler.dispatchMessage(Handler.java:103)
	at android.os.Looper.loopOnce(Looper.java:232)
	at android.os.Looper.loop(Looper.java:317)
	at android.os.HandlerThread.run(HandlerThread.java:85)
Caused by: com.google.android.exoplayer2.upstream.Loader$UnexpectedLoaderException: Unexpected RuntimeException: 403 error. You IP is temporarily blocked from accessing this video.
	at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:433)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
	at java.lang.Thread.run(Thread.java:1012)
Caused by: java.lang.RuntimeException: 403 error. You IP is temporarily blocked from accessing this video.
	at org.schabi.newpipe.player.datasource.YoutubeHttpDataSource.open(YoutubeHttpDataSource.java:501)
	at com.google.android.exoplayer2.upstream.DefaultDataSource.open(DefaultDataSource.java:258)
	at com.google.android.exoplayer2.upstream.TeeDataSource.open(TeeDataSource.java:52)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.openNextSource(CacheDataSource.java:786)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.open(CacheDataSource.java:599)
	at com.google.android.exoplayer2.upstream.StatsDataSource.open(StatsDataSource.java:84)
	at com.google.android.exoplayer2.source.chunk.InitializationChunk.load(InitializationChunk.java:99)
	at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:412)
	... 3 more

---

Additional context

[dosubot]

Hey there, @Kobaxidze256! 👋 I'm here to assist you with any bugs, questions, or contributions you have. Let's squash those bugs together!

There are two similar closed issues that might be relevant to your situation:

1. In one issue, a potential solution was suggested in a discussion thread. You can find more details here ^[1].

2. Another issue suggested that the problem might be related to an IP ban, possibly due to VPN usage on the main phone. This was referenced in issue [Bug] Video failed to play, 403 error #613 ^[2].

For your specific case, the "403 error" indicates that your IP is temporarily blocked by YouTube. This issue might be related to a bug that has been addressed in the latest app update (version 4.2.1), which includes a new extraction method to avoid being blocked by YouTube. Make sure you have updated to the latest version. Additionally, you can wait for the temporary block to expire or log in through the app's settings. If you are a supporter, you can use the Proxy feature to bypass IP blocks by enabling it in Settings with a valid token obtained through Ko-fi donations ^[3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[rancidfrog]

No popup this time, but in the log it shows ip blocked:

com.google.android.exoplayer2.upstream.Loader$UnexpectedLoaderException: Unexpected RuntimeException: 403 error. You IP is temporarily blocked from accessing this video.

Also, newpipe works fine.
I tried playing video, and again. Popup. Background.
Pipepipe will not play.
Strange, as I switched pipepipe because newpipe stopped playing videos for a while. And, now I have to switch back to newpipe as pipepipe stop working more often.

Exception

• User Action: play stream
• Request: Player error[type=ERROR_CODE_IO_UNSPECIFIED] occurred while playing https://www.youtube.com/watch?v=NXuzxbNGVZ4
• Content Country: GB
• Content Language: en-GB
• App Language: en_GB
• Service: YouTube (Anonymous)
• Version: 4.2.2
• OS: Linux Android 13 - 33

Crash log

com.google.android.exoplayer2.ExoPlaybackException: Source error
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleIoException(ExoPlayerImplInternal.java:641)
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:617)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loopOnce(Looper.java:201)
	at android.os.Looper.loop(Looper.java:288)
	at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: com.google.android.exoplayer2.upstream.Loader$UnexpectedLoaderException: Unexpected RuntimeException: 403 error. You IP is temporarily blocked from accessing this video.
	at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:433)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
	at java.lang.Thread.run(Thread.java:1012)
Caused by: java.lang.RuntimeException: 403 error. You IP is temporarily blocked from accessing this video.
	at org.schabi.newpipe.player.datasource.YoutubeHttpDataSource.open(YoutubeHttpDataSource.java:501)
	at com.google.android.exoplayer2.upstream.DefaultDataSource.open(DefaultDataSource.java:258)
	at com.google.android.exoplayer2.upstream.TeeDataSource.open(TeeDataSource.java:52)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.openNextSource(CacheDataSource.java:786)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.open(CacheDataSource.java:599)
	at com.google.android.exoplayer2.upstream.StatsDataSource.open(StatsDataSource.java:84)
	at com.google.android.exoplayer2.source.chunk.InitializationChunk.load(InitializationChunk.java:99)
	at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:412)
	... 3 more

---

[InfinityLoop1308]

Well, YouTube's A/B testing makes any service-related issues tricky to handle. The current situation is that we use the 'android' client to fetch video streams, while NewPipe uses the 'tvhtml5' client (which is also what we use in logged-in scenarios). Some people can’t use the android client (this issue), while others can’t use the tv client (#900, TeamNewPipe/NewPipe#11918, yt-dlp/yt-dlp#12563). YouTube is constantly updating their risk control strategies, so there’s no one-size-fits-all solution here—we have to keep updating to find a balance that makes the service stable.

For this issue specifically, aligning our extraction method with NewPipe’s isn’t difficult, but I’m worried that fixing it might affect even more people—at least right now, you can still log in to resolve it.
If anyone else is running into this problem, please leave a comment here so I can better assess what approach to take. We update much faster than NewPipe, so no need to worry about that.

[Kobaxidze256]

@InfinityLoop1308 why isn't it possible to try another method when one fails?

[InfinityLoop1308]

@Kobaxidze256 Because the client is unable to check if the stream URLs are valid - all the methods can return valid response and valid URLs, but only when you play them for a while you can find they are blocked.

[InfinityLoop1308]

That's why I'm considering adding a function to switch extraction method manually.

[Kobaxidze256]

@Kobaxidze256 Because the client is unable to check if the stream URLs are valid - all the methods can return valid response and valid URLs, but only when you play them for a while you can find they are blocked.

Videos won't start at all.

[Kobaxidze256]

Please reopen. I misclicked.

[misterhackerman]

Related: yt-dlp/yt-dlp#12746

YouTube has been updating its encryption every day recently, which has disrupted our parsing solution.
Until we find an effective workaround, please avoid logging in.

So u can't play with or without login now, YouTube is pushing it.
The function u talked about to switch extraction method is an amazing idea