New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning: "unable to extract player URL", error "No video formats found" #32583
Comments
See #32499. |
Hello Dirkf,
I followed your reply on Aug 11 in
#32499
*YT is now ignoring the ucbc=1 parameter that the extractor adds and
redirecting via consent.youtube.com <http://consent.youtube.com>, for some
pages. There is a fix but meanwhile try passing cookies from a browser
session where you have already gone through the consent check, using the
nightly build.*
- I've updated to the latest nightly build 2023.09.25
-- I expected that this would contain the *fix* you speak about in your
reply above but obviously it doesn't because I still get the error.
- So I continued with passing the cookies from the browser session:
-- I've cleared all cookies in my browser and consented to the YT-cookies
again.
-- I passed the cookies from the browser session as below
youtube-dl --add-header "Cookie:COOKIE_STRING_EXTRACTED_FROM_BROWSER" "
https://www.youtube.com/watch?v=UFfZHkrTw94"
but it didn't work. Neither worked replacing the
COOKIE_STRING_EXTRACTED_FROM_BROWSER with the actual cookie-content of the
header of the very first request which was "watch?v=UFfZHkrTw94".
Have I done it correctly/completely?
Any further ideas?
Thanks a lot for your response.
Cheers,
Jan
pá 6. 10. 2023 v 12:06 odesílatel dirkf ***@***.***> napsal:
… See #32499 <#32499>.
—
Reply to this email directly, view it on GitHub
<#32583 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDCUXSP5RRAWTQ525EMOSATX57JZZAVCNFSM6AAAAAA5VRNQDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJQGMZTEMZTGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Apparently not. The recommended procedure according to the FAQ is to use a browser extension to save a "Netscape format" cookie file from your recently logged-in browser session and pass the filename using The patch can be applied, or you could attempt to construct the cookie set by the patch. Or masquerade a non-EU IP address using a VPN. |
Hi Dirk,
thank you for your support.
The Netscape format cookie helped. This is a kind of a workaround and I
hope it is going to be fixed soon.
Cheers,
Jan
pá 6. 10. 2023 v 16:58 odesílatel dirkf ***@***.***> napsal:
… Apparently not.
The recommended procedure according to the FAQ is to use a browser
extension to save a "Netscape format" cookie file from your recently
logged-in browser session and pass the filename using --cookies. Manually
adding cookies may not work after #32450
<#32450>.
The patch
<#32499 (comment)>
can be applied, or you could attempt to construct the cookie set by the
patch. Or masquerade a non-EU IP address using a VPN.
—
Reply to this email directly, view it on GitHub
<#32583 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDCUXSPPPPQ7C3TRCSRU7HDX6AMCJAVCNFSM6AAAAAA5VRNQDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJQHAZTEMRZGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Checklist
Verbose log
Description
The text was updated successfully, but these errors were encountered: