ExoPlayer "Response code: 403" (Source error). Video middle/start. (Full local mode/DASH)

[executed]

Steps to reproduce

I would say I can reproduce the error more frequently when jumping from one video to other 5 times until the 1:00 minute mark but staying for some time on 5th or 5+nth video to observer the error.

Expected behavior

Preferred:

• Source error does not happen during video playback.
  Also acceptable:
• Error happens, but the playback is reloaded to same video position (at least it seems to be possible given that force-stop usually solves the issue and proceeds playing from old position).

Actual behavior

During the 1st quarter of video length/at the beginning I get "Source error" toast and video freezes.
Main error:
ExoPlayerImplInternal: Playback error
androidx.media3.exoplayer.ExoPlaybackException: Source error
Caused by: androidx.media3.datasource.HttpDataSource$InvalidResponseCodeException: Response code: 403
Video is black/stuck, permanently loading...

LibreTube version

0.27.1 (latest nightly)

Android version

Android 11 (Android TV)

Other details

One thing I've noticed is that the error is usually gone after app is force-stopped and same/other video is re-opened.
Then after couple of more videos usually in the 1st quarter of video length it pops up back again.
App force-stop - error gone again.

• When I do constant Google CDN ping through VPN interface and "Source error" occurs I see 0% packet loss, so internet connection seems stable.
• I would say mentioned 1:00 mark - I saw users I guess from NewPipe repo mentioning that when you not stay on video for at least a minute YT thinks you're a bot and throws 403, not sure if this is true or not.
• Attaching related errors from logcat.
  libretube_source_error_full_local.log
• Unfortunately I didn't succeed colleting packets via PCAPdroid to see wha's up on HTTP side.

Going through east european community 4pda I see ~10 users frustrated with this error.

Commenters input

Per user Figim:
"Http 403" (which may appear as a source error) is a playback error that occurs on all yt backends. Yt requires GVS potokens for streaming requests. NewPipe fixed this with PoToken support. (TeamNewPipe/NewPipe#11955) The PR on Libre-tube is based on this. It has not been merged yet and it is normal to have errors.
Figim additionally mentions that this issue might be duplicate of #7065.

Environment Details:
HLS: No
Full local mode: Yes
VPN: Proton Tier 0 servers through OpenVPN
DNS: Quad9 DoH with basic filtering

[Figim]

This is not fixed. Close the issue . It can be fixed: #7069

#7065

[executed]

This is not fixed. Close the issue . It can be fixed: #7069

#7065

#7065 mentions "bot http 403 etc." - I can only guess what this means.
This issue gives proper logs and descriptions unlike #7065, so unless someone can assure me #7069 fixes error described here, I would not close this one.

[Figim]

This is not fixed. Close the issue . It can be fixed: #7069
#7065

#7065 mentions "bot http 403 etc." - I can only guess what this means. This issue gives proper logs and descriptions unlike #7065, so unless someone can assure me #7069 fixes error described here, I would not close this one.

Explanation: "Http 403" (which may appear as a source error) is a playback error that occurs on all yt backends. Yt requires GVS potokens for streaming requests. NewPipe fixed this with PoToken support. (TeamNewPipe/NewPipe#11955) The PR on Libre-tube is based on this. It has not been merged yet and it is normal to have errors.

Additionally: VPNs are now blocked by YT and streaming without an account is not allowed

My issue: I have clearly listed the errors that occur without PoToken.

[executed]

@Figim It does not explain why force-stopping the app delays the "Source error" and even completely removes it until you start quickly switching between videos.

VPNs are now blocked by YT and streaming without an account is not allowed

This is not the case per my observations. Even when I get "Source error" and stay on same VPN server - issue is gone further confirming that VPN server IP is not getting blacklisted.

I would like to leave current issue opened. Especially that potential fix in #7069 is without updates for a month and is in Draft state. Reason is: it took me quite some time to search for some decent info explaining what's going on and I still had to create a new issue. I hope I'll save someone else's time.

The description was updated with your input and related issue.

[Figim]

@Figim It does not explain why force-stopping the app delays the "Source error" and even completely removes it until you start quickly switching between videos.

VPNs are now blocked by YT and streaming without an account is not allowed

This is not the case per my observations. Even when I get "Source error" and stay on same VPN server - issue is gone further confirming that VPN server IP is not getting blacklisted.

I would like to leave current issue opened. Especially that potential fix in #7069 is without updates for a month and is in Draft state. Reason is: it took me quite some time to search for some decent info explaining what's going on and I still had to create a new issue. I hope I'll save someone else's time.

The description was updated with your input and related issue.

This is the reason for the error. This issue will be closed anyway. There is no other solution to fix it. This is a yt blocking problem. You can't predict exactly how it will happen. Even if you observe it in different ways, the solution is that PR. We're aware of that. Dublicate, #7146

You have little knowledge about this issue, so different opinions come to your mind.

[executed]

Potential fix in #7069 was merged.
Don't have time for it yet, but I plan to sync my custom branch with master to test if this fixed the "Source Error".