[GH-ISSUE #1142] Sometimes YouTube video/audio ends up being 0 bytes #3639

Closed
opened 2026-04-13 12:10:26 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @wukko on GitHub (Mar 6, 2025).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/1142

Originally assigned to: @wukko, @dumbmoron on GitHub.

bug description

noticed a lot of random errors recently (you can see them at https://status.cobalt.tools too). sometimes same exact videos with same client & settings get 403d by googlevideo.

we're already looking into a way to go around this, but for now trying several times works.

you can subscribe to notifications on this issue to get notified when it's closed

Originally created by @wukko on GitHub (Mar 6, 2025). Original GitHub issue: https://github.com/imputnet/cobalt/issues/1142 Originally assigned to: @wukko, @dumbmoron on GitHub. ### bug description noticed a lot of random errors recently (you can see them at https://status.cobalt.tools too). sometimes same exact videos with same client & settings get 403d by googlevideo. we're already looking into a way to go around this, but for now trying several times works. *you can subscribe to notifications on this issue to get notified when it's closed*
GiteaMirror added the main instance issue label 2026-04-13 12:10:26 -05:00
Author
Owner

@wukko commented on GitHub (Mar 6, 2025):

should be fixed by #1143! if youtube health checks don't error out within a few hours, i'll close this issue

<!-- gh-comment-id:2704560822 --> @wukko commented on GitHub (Mar 6, 2025): should be fixed by #1143! if youtube health checks don't error out within a few hours, i'll close this issue
Author
Owner

@hextor1 commented on GitHub (Mar 6, 2025):

I am also facing this issue still

<!-- gh-comment-id:2704973166 --> @hextor1 commented on GitHub (Mar 6, 2025): I am also facing this issue still
Author
Owner

@wukko commented on GitHub (Mar 7, 2025):

this is about the main instance, and everything’s been fine ever since the fix

<!-- gh-comment-id:2705398561 --> @wukko commented on GitHub (Mar 7, 2025): this is about the main instance, and everything’s been fine ever since the fix
Sign in to join this conversation.