Failed to extract signature decipher algorithm [YouTube]

[bandicuttt]

problem description

When trying to download any video or shorts from youtube I get this error

[YOUTUBEJS][Player]: Failed to extract signature decipher algorithm.

Ran it on different platforms

[nicolaigaina]

having the same issue when I run cobat api instance locally

[wukko]

this error doesn’t affect cobalt as it doesn’t decipher anything. it’s fixed in the dev branch and will be merged soon!

[bandicuttt]

just wanted to write that yt-dlp has already rolled out the update. Waiting for the merge

[wukko]

merged into main

[jo-chemla]

Issue is still present on latest cobalt 7 docker image: image: ghcr.io/imputnet/cobalt:7
Would it be possible to apply the yt-dlp update to cobalt api v7 as well? Thanks!

[wukko]

Would it be possible to apply the yt-dlp update to cobalt api v7 as well

cobalt doesn’t use yt-dlp, and v7 is no longer supported. i advise you to switch to v10 and use that instead, along with future latest releases

[jo-chemla]

I cannot switch to v10 because I need a fully self-hosted cobalt, not only the instance but the frontend as well - see here #768 and there #722

Seems that the simple fix is to update cobalt v7 package.json so the minimum required youtubei.js (rather than yt-dlp) version starts from YouTube.js/releases/tag/v12.1.0 onwards, released on Dec 10 2024 with fix Fix signature algorithm extraction as shown in this thread LuanRT/YouTube.js#831

For example, cobalt v10 uses "youtubei.js": "^13.1.0" see here

[wukko]

but the frontend as well

you can still self host it, but since it's a static build, it's not in a docker image. here's how to build it: https://github.com/imputnet/cobalt/tree/main/web#configuring (run pnpm install first)

Seems that the simple fix is to update cobalt v7

it makes no sense for me to update the v7 source code if v10 is better in every single way. v7 is not supported anymore. if it breaks, it's not really my responsibility as it's no longer maintained.

[jo-chemla]

Thanks for the feedback, understood - sad given how simple the fix is, but it might indeed introduce breaking changes which would incur more than just the version bump.

The general consensus around v10 in the referenced issues seems to be that most self-hosters that had a working docker-compose setup on v7 won't switch unless there are built images available to ghrc/docker-hub or any other image repo that makes it as easy to deploy, without requiring to build the image one-self.

But thanks for pointing towards these instructions!