Sign in to confirm you’re not a bot. This helps protect our community. Learn more

[randomscumbag]

First time seeing this. I am logged into my youtube and to my spotify, is their something else I need to log into? Sources for the tracks are their, just not going through with the downloads.

• [01 Deepest Truth ‒ Morgin Madison]
| ➤ Collating sources...
| ➤ [•] YouTube Music...(failed: [Response code 404 (Not Found)])
➤ [•] YouTube...[success, found 2 sources]
| ➤ Awaiting audiofeeds...(failed: [ERROR: [youtube] laJjJDtF-TE: Sign in to confirm you’re not a bot. This helps protect our community. Learn more])

[miraclx]

Hi @randomscumbag, do you still encounter this?

I'd expect it to be a one-off, but from our side, there's not much we can do.

One option is to allow you to attach your YouTube cookies, but I'm not a fan of that approach as it *may* associate your account with bot-like behavior, and risk getting banned.

[Treytcg]

Hi there,

I’ve been trying to implement the feature using tough-cookie and editing the youtube.js file to use cookies from a fake YouTube account, but I’m having trouble getting it to work. Is there a way I can implement this on my end? I'm pretty new to this, so any help would be greatly appreciated.

Thanks in advance!

[miraclx]

So this particular issue is from youtube-dl, you can add the appropriate flags here:

freyr-js/src/services/youtube.js

Lines 56 to 62 in 559f2bf

	youtubedl(null, {
	'--': [url],
	socketTimeout: 20,
	cacheDir: false,
	dumpSingleJson: true,
	noWarnings: true,
	});

Youtube-dl has the following cookie-args:

    --cookies FILE                  Netscape formatted file to read cookies from
                                    and dump cookie jar in
    --no-cookies                    Do not read/dump cookies from/to file
                                    (default)
    --cookies-from-browser BROWSER[+KEYRING][:PROFILE][::CONTAINER]
                                    The name of the browser to load cookies
                                    from. Currently supported browsers are:
                                    brave, chrome, chromium, edge, firefox,
                                    opera, safari, vivaldi, whale. Optionally,
                                    the KEYRING used for decrypting Chromium
                                    cookies on Linux, the name/path of the
                                    PROFILE to load cookies from, and the
                                    CONTAINER name (if Firefox) ("none" for no
                                    container) can be given with their
                                    respective separators. By default, all
                                    containers of the most recently accessed
                                    profile are used. Currently supported
                                    keyrings are: basictext, gnomekeyring,
                                    kwallet, kwallet5, kwallet6