openssl not available for download
See original GitHub issueToday on creating a new project, failed to download openssl:
[INFO]: Downloading openssl from https://www.openssl.org/source/openssl-1.1.1.tar.gz
Traceback (most recent call last):
...
ValueError: read of closed file
As of 2020-03-31 openssl-1.1.1.tar.gz is uploaded no longer: Downloads (it’s openssl-1.1.1f.tar.gz now)
Where am I supposed to change the file name?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (5 by maintainers)
Top Results From Across the Web
How to install OpenSSL in windows 10? - Stack Overflow
All downloads listed there are 3rd party compilations of OpenSSL and thus are not official. The site even states it itself: "Use these...
Read more >Installing OpenSSL on Windows 10 and updating PATH
Here I will teach you to do the following: Install OpenSSL; Add OpenSSL to your PATH. Install OpenSSL. This step is a ...
Read more >Fixing - Facebook Unity SDK - Gley Tips #7 - YouTube
Fix for: OpenSSL not found. Make sure that OpenSSL is ... Also a fix for: Keytool not found. ... Open SSL available to...
Read more >OpenSSL
To get the latest news, download the source, and so on, please see the sidebar or the buttons at the top of every...
Read more >How to solve issues with OpenSSL when trying to run ...
json (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) ##troubleshooting. I have OpenSSL downloaded (the newest ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, probably there’s a (DNS based) load balancer and an endpoint is having difficulties: As you can see, I’m downloading from a different endpoint. 😄
I think the issue is gone, and was also related with a temporary hiccup of the provider. Feel free to reopen to discuss it further otherwise