Video doesn't play beyond 50-60 seconds. 403 Error, YouTube IP Ban

[ticklemyIP]

Checklist

• I am able to reproduce the bug with the latest version.
• I am not able to reproduce the bug with the latest version of vanilla NewPipe.
• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the vanilla NewPipe contribution guidelines.

Affected version

0.27.2

Steps to reproduce the bug

Play video
At around 50-60 seconds Error

Expected behavior

Video plays without issue

Actual behavior

Video doesnt play beyond mentioned timeframe

Screenshots/Recordings

No response

Logs

Exception

• User Action: play stream
• Request: Player error[type=ERROR_CODE_IO_BAD_HTTP_STATUS] occurred while playing https://www.youtube.com/watch?v=0toWysEA3vs
• Content Country: US
• Content Language: en-US
• App Language: en_US
• Service: YouTube
• Version: 0.27.2
• OS: Linux Android 14 - 34

Crash log

com.google.android.exoplayer2.ExoPlaybackException: Source error
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleIoException(ExoPlayerImplInternal.java:644)
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:616)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loopOnce(Looper.java:230)
	at android.os.Looper.loop(Looper.java:319)
	at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: com.google.android.exoplayer2.upstream.HttpDataSource$InvalidResponseCodeException: Response code: 403
	at org.schabi.newpipe.player.datasource.YoutubeHttpDataSource.open(YoutubeHttpDataSource.java:422)
	at com.google.android.exoplayer2.upstream.DefaultDataSource.open(DefaultDataSource.java:263)
	at com.google.android.exoplayer2.upstream.TeeDataSource.open(TeeDataSource.java:52)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.openNextSource(CacheDataSource.java:796)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.open(CacheDataSource.java:609)
	at com.google.android.exoplayer2.upstream.StatsDataSource.open(StatsDataSource.java:84)
	at com.google.android.exoplayer2.source.chunk.ContainerMediaChunk.load(ContainerMediaChunk.java:124)
	at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:412)
	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)

---

Affected Android/Custom ROM version

Android 14

Affected device model

Samsung Galaxy A52s 5G

Additional information

I'm using a respected VPN service

[Ty3r0X]

Bump, also experiencing this issue!

[ticklemyIP]

Bump, also experiencing this issue! @Ty3r0X

Tubular has been 2 versions behind, one of the PRs in the immediate next release of NewPipe solved this issue. As the app is no longer (or not currently) maintained I recommend moving back to NewPipe ore another suitable alternative.

[codeXXjs]

Bump, also experiencing this issue! @Ty3r0X

Tubular has been 2 versions behind, one of the PRs in the immediate next release of NewPipe solved this issue. As the app is no longer (or not currently) maintained I recommend moving back to NewPipe ore another suitable alternative.

If this is true then it quite sad. I love the extra features it offers. Let's hope there's an update.

[leoossa]

I found a temp fix that often (not always works):
You have to kill the app (not turn it off, but kill it), open it again, open different video, let it play / buffer (probably it has something to do with caching), and then open desired video again.
Works ~85% of time.
It also happens to me when switching between Wi-Fi and cellular data.

[singh9596]

+1. Additionally switching between networks breaks the video with error.

[HairyMilkshakes]

In case you're wondering why: yt-dlp/yt-dlp#11868

[ticklemyIP]

Just so I don't abandon this issue: to be fair NewPipe has a new similar issue just like this one. But at least they patched the one Tubular has. Just to keep that in mind. Jan 12, 2025, 18:25 by ***@***.***:

…

In case you're wondering why: > yt-dlp/yt-dlp#11868 <yt-dlp/yt-dlp#11868> — Reply to this email directly, > view it on GitHub <#189 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/A6GRZTPNYRXCGSMGAKIR4BD2KKQPZAVCNFSM6AAAAABU2ALTSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBVHA2DCNRTG4>> . You are receiving this because you authored the thread.> Message ID: > <polymorphicshade/Tubular/issues/189/2585841637> @> github> .> com>

[ticklemyIP]

Namely TeamNewPipe/NewPipe#11803

[codeXXjs]

The patch has been fixed.

[asandikci]

Not completely. Will be solved completely with TeamNewPipe/NewPipe#11955

[funsafe-ptr]

https://github.com/polymorphicshade/Tubular/releases/tag/v0.27.6 👍

[asandikci]

This should be solved with latest release