mirror of
https://github.com/imputnet/cobalt.git
synced 2026-05-22 06:18:25 -05:00
[GH-ISSUE #992] Can't download stuff from YouTube, cobalt says it's disabled or returns 0 byte files #5011
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bridgetpenpen on GitHub (Dec 12, 2024).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/992
bug description
every time i download any video the bytes are 0 off youtube
reproduction steps
1 go to youtube
2 copy and paste link into cobalt
3 hit the arrows to download
4 see that the files have 0 bytes on them
screenshots
links
No response
platform information
window 10 on chrome/google on ios
additional context
No response
@hamidb80 commented on GitHub (Dec 12, 2024):
same here
@mts1234a commented on GitHub (Dec 12, 2024):
if you can't fix this, i'll assume this is a useless link
@Aaronlalala commented on GitHub (Dec 12, 2024):
Same here.
@wukko commented on GitHub (Dec 12, 2024):
we've been aware of the issue since the very beginning (approx 4 hours ago). it's not caused by us and is not an issue with cobalt's code, youtube blocked all of our ip ranges this morning.
we're currently doing our best trying to come up with a solution to restore downloads from youtube asap. we're sorry for any inconveniences caused in the meantime :(
as a temporary measure, you can try self-hosting a cobalt processing instance on your computer or home server: https://github.com/imputnet/cobalt/blob/main/docs/run-an-instance.md
i've temporarily disabled youtube support on the main instance, so that you don't get 0 byte files.
@ogohogo commented on GitHub (Dec 12, 2024):
beside ip blocking they send abuse messages, be careful :)
@wukko commented on GitHub (Dec 12, 2024):
i'm soooo scared of a baseless threat by google
(thank you for the warning though)
@cheekyrandom commented on GitHub (Dec 12, 2024):
think i possibly contributed to this issue LOL
@rnxm commented on GitHub (Dec 12, 2024):
fuck google
@Sainan commented on GitHub (Dec 12, 2024):
Might it be possible to setup Mullvad on the processing servers to bypass the IP blocks? I know a VPN is a bit tricky on servers due to incoming traffic, but not impossible.
@CallMeVerity commented on GitHub (Dec 12, 2024):
@Sainan I actually have Gluetun setup in a docker container which uses Mullvad, I then connect it to the Cobalt API instance that is also running in a docker container. This worked for me but not for very long, the IP's eventually get blocked (pretty quickily too).
@Sainan commented on GitHub (Dec 12, 2024):
Set it up to automatically switch Mullvad servers every hour. 🙈
@CallMeVerity commented on GitHub (Dec 12, 2024):
I assume you're joking, but if not, rotating proxies might actually be a better solution than a VPN.
@Sainan commented on GitHub (Dec 12, 2024):
I'm not joking. It's what we did for checking a certain anti-cheat provider for information about bans. They did not like that we were providing transparency into their business. After deploying this Mullvad approach, they seemed to stop bothering.
@CallMeVerity commented on GitHub (Dec 12, 2024):
Wouldn't you eventually run out of servers to use on Mullvad? Plus, YouTube could end up blocking their ASN altogether. A rotating proxy might be a more sustainable solution for something like this.
@Sainan commented on GitHub (Dec 12, 2024):
The idea is that legit users still use Mullvad, so blocking them outright might be less ideal.
@CallMeVerity commented on GitHub (Dec 12, 2024):
I think you're right in that they wouldn't block them outright. Still a possiblity since it is Google we're talking about. Regardless I think running a VPN over the entire instance would be slow, potentially cause issues with other services and be somewhat useless since the time it takes YouTube to block the IP is inconsistent, so changing server every 1 hour wouldn't be a solution.
@tayfrm99 commented on GitHub (Dec 13, 2024):
true, they also move their servers around quite often
@WorriedArrow commented on GitHub (Dec 13, 2024):
Seems to work now..?
@vergiliusmaximus commented on GitHub (Dec 13, 2024):
Working now 👍 thanks a lot. Imma donate when I can
@vergiliusmaximus commented on GitHub (Dec 13, 2024):
yup working now
@wukko commented on GitHub (Dec 14, 2024):
as others have mentioned, it's been fixed for a few days (since evening of 12th), but we made sure to get backups so this doesn't happen again in the future. can never be sure with youtube though.
@PurpBatBoi commented on GitHub (Dec 14, 2024):
6:16pm, dec14, its broken again 😔
@SleepyPeko commented on GitHub (Dec 14, 2024):
still getting 0b over here. ig youtube links are still broken
@SleepyPeko commented on GitHub (Dec 14, 2024):
anyways, ight imma go selfhost cobalt
@ieatwaffle commented on GitHub (Dec 15, 2024):
Hello! i created an account just to say that issue is still persistent with YouTube links. I was able to download SoundCloud links but YouTube doesn't seem to be working at the moment again.
@wukko commented on GitHub (Dec 15, 2024):
fixed again, it happened deep at night, almost intentionally
@marco-lee-datax commented on GitHub (Jan 22, 2025):
@wukko Did you deploy this solution? Can you please share with us how you fixed it? Thank you so much!
@Chonkblonk commented on GitHub (Jan 30, 2025):
I appear to be experiencing an issue like this, I am getting a 0 byte file, but most peculiarly, what I am being provided is a 0 byte .txt file, for whatever reason.
Now, I want to be clear also that I have not somehow managed to change anything on my end to make my computer think that .mp3 files are to be opened with Notepad.exe, because that is not what is happening on my end. It seems that either Cobalt or Firefox interprets the file in question as being a .txt file.
@wukko commented on GitHub (Jan 30, 2025):
@Chonkblonk can you try again?
@Cattrag commented on GitHub (Jan 31, 2025):
now im getting it too...
@Chonkblonk commented on GitHub (Jan 31, 2025):
The funniest thing, is that just a few minutes after sending this, I tried again, and then suddenly it worked.
Sorry, should have replied back sooner.