Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Signature extraction failed as of 1/29 update #11890
Comments
Mochlate
changed the title
|
|
|
Same failure here. Uinstalled and then reinstalled and updated. Worked fine yesterday, about 20 hours ago. |
|
Same issue, Looks like it's extracting the wrong signature url, it's grabbing "/yts/jsbin/player-en_US-vflV3n15C/base.js" on line 971 Edit: Sorry, I'm on version 2017.01.29, Python 3.6.0, Linux-4.9.6-1-ck-haswell-x86_64-with-arch |
|
Same here. Had it on the older version too, though. |
|
+1 Im getting it on |
|
Yeah, the 1.10 update had it as well but they patched it up within hours. So hopefully the same happens here. They apparently don't test well after they update :/ Here: |
|
Seeing failures on version |
|
yep, same issue here. it seems the /yts/jsbin... path is treated as absolute, but it should be prefixed with the domain. |
|
Same issue with me too. |
|
Bot begins to type and stops, if that helps at all |
|
Ughh getting this issue |
|
I just did a batch download of some 10ish youtube urls but only 1 of them spat out this same error.
|
|
@LeLobster Right, doesn't happen everytime. It appears to be random, as it happens on/off for the same song. |
|
@Mochlate I couldn't get any vevo videos to work by retrying. For instance I ran this 10 times: |
|
I have the same error as well - I've pasted a stacktrace as a gist, in case it's helpful. |
|
Endpoint was discontinued. New Endpoint is supposed to be |
|
@CyberiumShadow This doesn't have to do with the endpoint you are saying is discontinued, if you read about the issue google has rolled out a change (apparently) that is giving youtube player base links without the host. Edit: This change was rolled out some days ago as far as I can tell, since this was spotted and fixed some days ago on another lib/software I use. |
|
Looks like this is where the bulk of this issue, I'll post my findings from what I posted on another issue, here instead: Figured I'd submit this here instead of making my own issue, here's a replicatable URL I get this consistently on that is freely accessible: And version output: Through testing I seem to get this with any playlist I test, and normal videos every now and then. When 's' is found in the url data that is passed, such as with the URL I gave, here's the url_data returned From what I can tell, the url is just missing I edited this to test it, and it looks like simply adding that worked, however now there's an error with parsing the signature: I checked this out as well, and based on the same example I was using above, the url it's supposed to be parsing is this one: https://www.youtube.com/yts/jsbin/player-en_US-vflV3n15C/base.js And the regex it's looking for is indeed not there. This is where I stopped investigating, because I could not for the life of me figure out where the signature is inside of here. |
|
Take a look with my pull request, I tested it work fine with some videos, I think there just a little bit change from YouTube, and the old regex is no longer working so I replaced it. |
|
I've given the changes in that pull request a try, and yes it indeed fixes the issue experienced. |
|
Made an account to post that I am having an issue with this as well. ERROR: Signature extraction failed: Traceback. used the --verbose flag and got the following: Initially I thought that there was a conflict created as I recently installed ffmpeg. However, even after a reinstall and reupdate of the youtube-dl line, I'm still getting the error. Figured I'd post here rather than making a whole new thread. |
|
I too have this update, and I also get the Signature extraction error. |
|
Got the same stuff: During handling of the above exception, another exception occurred: Traceback (most recent call last): |
|
same issue.. |
|
Same issue here, I think it's trying to get the wrong base.js |
|
seems like it fixed now. Many thanks!!! |
and others
Updating to the 1/29 release is now yielding this error! Major error.