[YouTube] HTTP error 403 around 1 minute mark

[opranda]

Please also see About YouTube playback errors - YouTube changed some things to get working streams

---

Checklist

• I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
• 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 contribution guidelines.

Affected version

0.27.0

Steps to reproduce the bug

When I click play, the video loads and the message "Network error" appears and nothing happens

Expected behavior

No response

Actual behavior

No response

Screenshots/Screen 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=GnUCGS0KRqM
• Content Country: RU
• Content Language: ru-RU
• App Language: ru_RU
• Service: YouTube
• Version: 0.27.0
• OS: Linux Android 5.1 - 22

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:107)
at android.os.Looper.loop(Looper.java:194)
at android.os.HandlerThread.run(HandlerThread.java:61)
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.InitializationChunk.load(InitializationChunk.java:99)
at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:412)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)

---

Affected Android/Custom ROM version

No response

Affected device model

No response

Additional information

No response

[MDP43140]

Did you try different video, on different device or network? I got this problem too where it stuck buffering no matter what quality or video/audio playback, it persists in Firefox, yt-dlp (i use Seal) and many other 3rd party apps, I can only watch said content on YouTube mobile or Chromium-based browsers

[tag27]

The strangest thing in my case is that, at first, I didn't have this problem, but from about two~three days ago until now it appears from time to time. But I notice that it's more frequent in case I use pip mode or when I put the video in the background.

OS: Android 12, One UI 4.1
Device: Samsung Galaxy A11 (SM-A115M/DS)

[Baltazar500]

@tag27, Maybe YouTube is reconfiguring its servers? After the 22nd format was removed yt-dlp/yt-dlp#10206 NewPipe worked fine. There are no problems at the moment. Perhaps you have a "forbidden/403" format in pip at the moment? Try changing the quality

[techno156]

Maybe YouTube is reconfiguring its servers? After the 22nd format was removed yt-dlp/yt-dlp#10206 NewPipe worked fine. There are no problems at the moment. Perhaps you have a "forbidden/403" format in pip at the moment? Try changing the quality

This looks to be be part of it, since I've also run into something similar, but only encounter the issue with background play (haven't tested with picture-in-picture). Regular video playback works fine.

Quick guess and a poke around the error NewPipe brings up, along with it working fine if the video is loaded through other formats, would suggest that it's an issue with it being able to load the DASH segments properly for the background/PIP format. It can grab the first segment fine, but nothing else past that, hence playback being relatively early on in a video.

[nash268]

for me when error occurs it's always at 00:59 time stamp.

[juanfra684]

Can you test with a different DNS? I had problems with some providers, but Quad9 works fine. After changing the DNS, don't forget to disconnect/connect and close/open NewPipe.

IPv4
9.9.9.9
149.112.112.112

IPv6
2620:fe::fe
2620:fe::9

DoH
https://dns.quad9.net/dns-query

DoT
dns.quad9.net

[krushia]

Confirming that:

1. The first part of a video will play before the error occurs
2. After the error, the triggering video will no longer play at all
3. After the first occurance, there appears to be an increased probability of triggering the error with other videos (but they may still play okay)
4. Restarting NewPipe usually fixes it
5. It happens sporadically

[juanfra684]

Clearing the metadata in the settings menu fixed the problem for me. I didn't change the DNS or anything this time.

[1xFF]

Many users are reporting a 403 at around one minute of playback, these issues are being marked as duplicates of this issue. However this issue has significant differences in both the steps to reproduce and traceback line numbers. It's possible that these are seperate issues.

[tag27]

Many users are reporting a 403 at around one minute of playback, these issues are being marked as duplicates of this issue. However this issue has significant differences in both the steps to reproduce and traceback line numbers. It's possible that these are seperate issues.

I believe both it's the same problem, because possibly the OP of this issue didn't notice that the video paused before completing 1 minute. I hadn't realized it myself when I commented earlier.

[opusforlife2]

Until we know for sure that they are different issues, both 403 errors are being treated as the same.

[techno156]

Confirming that:

1. The first part of a video will play before the error occurs

2. After the error, the triggering video will no longer play at all

3. After the first occurance, there appears to be an increased probability of triggering the error with other videos (but they may still play okay)

4. Restarting NewPipe usually fixes it

5. It happens sporadically

I've found that if you do trigger the error, coming back to the video later (either from playing another file, or by restarting the app), and starting from that point doesn't run into that issue again, despite it being the same video.

YouTube Music uploads (the ones that are just album art rather than an actual video) don't seem to trigger it either, maybe they use a different format that doesn't have the same problems?

[acarasimon96]

YouTube Music uploads (the ones that are just album art rather than an actual video) don't seem to trigger it either, maybe they use a different format that doesn't have the same problems?

In my experience, both normal and YouTube Music videos are affected; I get the same exact behavior on either kind.

[NoahJelen]

I have an idea for a workaround: Make a PR that causes NewPipe to automatically wipe the metadata cache and begin replaying the video from wherever it left off at every time this error occurs since wiping the metadata cache (in Settings -> History and Cache -> Wipe Cached Metadata) seems to make this issue go away temporarily.

[TechnologyClassroom]

I said this in one of the other linked threads: Google seems to be A/B testing a number of things recently. SponsorBlock noted that one of those things is server-side ad injection which is changing the length of the videos.

[alliethebanana]

So this may or may not be helpful.
Around the time I started being unable to play videos through Newpipe, I went to my smart TV instead to try to stream videos through SmartTube beta, and lo and behold, now there is a 403 error code whenever it tries buffering the videos.

So it could be as some people have mentioned in the thread that Google is experimenting with things server side to block requests from adblocking clients

[ACR-Jeff]

The only thing I can get working is other apps that utilize the invidious instances, Everything else just fails