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.
`youtube-dl -U` fails to update on outdated machines due to SSL protocol version - consider using http fallback #15497
Comments
|
I prefer 1 or 2. As the updater function already checks RSA signatures, so using unencrypted HTTP is not a big problem. By the way, I think it's time to move away from RSA 1024. Side notes:
[1] https://www.ssllabs.com/ssltest/analyze.html?d=rg3.github.io&s=151.101.53.147 |
|
There is already |
|
I have the same problem on my debian server
|
|
I had the same problem. I even reinstalled
It works beautifully. Here's the output of a 4k video, using highest audio and video:
|
Might do; although I would also add a message telling the user to do that whenever https fails. |
|
|
|
@PacoH did your even read my post? It's not respected currently. |
|
You mean |
|
|
|
It sounded like you were making a recommendation to use |
|
Was any work-around ever settled-on? Is really a drag to have to check this every week for an update. |
|
I don't know why this is closed. The issue still persists with version 2018.02.04 as installed with
Current version:
I installed the latest version with
This installs it if it isn't already installed, and updates it after that. The
|
|
@PacoH: Commit 7d2b4aa fixes this issue by adding support for the
I would've preferred something to notify users about this |
|
OK. Thanks. I tried it and it works exactly as advertised. It still seems strange that using I downloaded
|
|
$ youtube-dl -U --prefer-insecure |
|
This works:
|
|
Thanks, I was able to upgrade using brew, but even after updating to 2018.05.18, I get: |
|
How did you do that? I tried:
I have found that the NOTE: I had already updated it using |
|
I'm using Python 3.2 and was having ssl errors due to TLS version. ctx = ssl.SSLContext(ssl.PROTOCOL_TLSv1_2) |
|
I had this problem with 2017.12.02 on my MacBook (Yosemite), so manually removed that version of youtube-dl, and installed fresh with the But the problem persists. This is what I see:
At least I know how to manually update the app now, but it's a shame the |
|
I'm getting a new error today that is asking me to make a bug report, but also reminding me to make sure I'm using the latest version. |
|
If you use Homebrew you don't need to update with |
Heeeeeey thanks to your comment, I got to update from the Nov 2017 version ;) |

Please follow the guide below
xinto all the boxes [ ] relevant to your issue (like this:[x])Make sure you are using the latest version: run
youtube-dl --versionand ensure your version is 2018.02.04. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.-Uoption)Before submitting an issue make sure you have:
wgetthat page as http rather than https and it worked.What is the purpose of your issue?
If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output:
(NB: I also tried running youtube-dl under python 2.7.0 and 3.1.2 without success.)
Description of your issue, suggested solution and other information
I have a rather old computer with a rather out-of-date system, and since recently I can't update youtube-dl. This might be due to github.io changing its SSL protocol and requiring a more advanced standard that my PC has trouble with. (This is partly due to the fix for bug #5909 which required https for the update, although this was working before (up to 2017.12.14) so I guess it has to do with github and not youtube-dl.)
I can think of 3 solutions (assuming the SSL protocols cannot or shall not be changed):
--update-httpor-U --allow-http-update, to ensure they know what they're doing. (Additionally, detect if this was an SSL error and in that case tell the user to use this option, rather than showing that "try again later" message.)(It should be noted that if someone is affected by this, these solutions will not be effective unless they reinstall manually.)