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.
certificate verify failed _ssl.c: 720 #12348
Comments
|
I guess you're using XX-net or other GAE (Google App Engine) based proxies? If so --no-check-certificate is the only solution. |
|
yeach, I'm using GAE as proxy, but it worked well before. I dont remember the exact version, since I upgrade, I got the problem. Is there a way to roll back a lower version of youtube-dl |
That's interesting. Maybe you were using some older Python versions before? Certificate verification wasn't enabled until Python 2.7.9. |
|
Yeah, it is the python 2.7.9 |
|
Do you mean 2.7.9 works but 3.5.3 fails? I might be inaccurate. I meant, In Python 2.x, up to 2.7.8, doesn't verify certificates, so there won't be errors. Since 2.7.9, it would work the same as all 3.x versions. |
|
I don't remember the exact version, but definitely is either 2.7.9 or 3.4. Because my computer only have these two version python when youtube-dl worked fine. And in March 3, 3rd, I installed 3.6 version, and then 3.5 versioned, and in these two version I use I try different solutions, the problem keep switch from ssl.c 600 to ssl.c 720. Note, I try to solve ssl.c 600 use comment, and didn't work. When was certificates verification added to youtube-dl? Is it always there? My environment is completed messy. |
Yes it's always there. The verification is performed by the underlying Python, not youtube-dl. Could you paste verbose logs of |
|
I have updated all the youtube-dl to the version 2017.3.02, so now they all not working. And the working case related to a older version of youtube-dl. Is there a link to download the old version youtube-dl, so I could try to reproduce the working logs. |
|
In https://rg3.github.io/youtube-dl/update/versions.json, there are URLs of versions since 2012.02.22. Please tell me if you need even older versions. |
|
This is fair enough. Now I will try to reproduce it. |
|
Well, lots of URLs in versions.json are dead. Specificially, files uploaded before #9690 are not moved to Github, so they'll end up with 404. Files on https://pypi.org/project/youtube_dl/#history are still fine. As you're already using pip, you can install old versions with ==. For example:
|
|
I have try many version of youtube-dl, but the problem cant reproduce. And I switch different proxy the problem is gone. SO the problem is the the proxy I'm using(There must something changed, but I can't roll all the things back). And the problem is beyond the scope of youtube-dl, So I just use no-check-certificate. Very appreciate your help. |
|
OK. I'll closing it first as apparently it's not directly related to youtube-dl. Feel free to post your new findings if any. |
Please follow the guide below
xinto all the boxes [ ] relevant to your issue (like that [x])Make sure you are using the latest version: run
youtube-dl --versionand ensure your version is 2017.03.02. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.Before submitting an issue make sure you have:
What is the purpose of your issue?
The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to 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 as follows:
Add
-vflag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):Description of your issue, suggested solution and other information
running youtube-dl in win 10 and the python version is 3.5.3. I have searched many issue about certificate very failed, and try the comment1 and other methods, but they don't work. And I notice the verify failed number is
verify failed (_ssl.c:720), is different from what have posted, like 600, 581 and more. I have use google to search the exact number on the issues, and found none.if add the flag --no-check-certificate, it will work.