emsdk install failing

I am trying to update my emsdk installation and getting the following error after running ./emsdk install latest.

Installing tool 'emscripten-1.37.34'..
Error downloading URL 'https://github.com/kripken/emscripten/archive/1.37.34.tar.gz': <urlopen error [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:590)>
Installation failed!

I'm seeing this whether I try to upgrade an existing installation or install from a clean copy of the SDK. Platform is macOS. I tried to install 1.37.33 as well and that failed with the same error. Is anyone else seeing this problem?

Yes I have the same problem but with emscripten-1.37.35
Error downloading..
I'm on windows.

Similar problem.
Platform: windows
Error downloading URL 'https://github.com/kripken/emscripten/archive/1.37.35.zip': <urlopen error [Errno 1] _ssl.c:504: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version>

However, i was able to download the archive manually from the browser. Is there a way to bypass the download stage(maybe put the archive to a specific directory manually) and install directly?

@jjyyxx

@jjyyxx Put the zip in the zips folder and make sure it has the same file name as in the URL (i.e. 1.37.35.zip, not emscripten-1.37.35.zip). Then run the install command again and it will detect that the zip file is already downloaded.

That's a good workaround, thanks!

Thanks. It works perfectly

This seems to have been caused by https://github.com/blog/2507-weak-cryptographic-standards-removed. The version of Python included in the Windows build is too old.

Edit: It's because of the included version of OpenSSL is too old (i.e. less than 1.0.1).

Sounds like we need to update the Python in the windows emsdk, but is this windows-only? The initial report here was on Mac.

Yep I’m seeing this on macOS 10.12 and 10.13.

Is the core issue the same, do those MacOS versions ship with too-old versions of python?

Python version is 2.7.10 on both macOS versions I've tried, I guess that must be too old if that's the issue.

Just updated to MacOS 10.13.3 and the install latest command worked!

Adding some things I saw, which may or may not be helpful. tlsv1 alert protocol version error searches reveal mostly python and openssl issues. I noticed before the MacOS upgrade I was running openssl 0.9.8 but now I'm running LibreSSL 2.2.7.

kripken - yes it's an issue on windows too. I also got this error when trying to compile a project that worked fine in 1.35.00

urllib2.URLError: <urlopen error [Errno 1] _ssl.c:504: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version>

Sorry, I missed that it was originally reported on macOS, as I had the same issue on Windows.

It's actually the version of OpenSSL that's too old (version 1.0.1 or higher is needed for TLS 1.2). Python 2.7.5 for Windows includes OpenSSL 0.9.8y, and macOS 10.13.3 includes OpenSSL 0.9.8zh.

Yep, I've retried on macOS 10.13 and it does seem to work so it's just 10.12 where I have the problem (Which is my main development machine). I'll use the workaround that was posted until I get round to upgrading. Thanks for the responses!

@juj

Seems like emsdk is still using Python 2.7.5.3 and that it still has this issue. I just tried it today and installed Python 3.6.5 before because emsdk wouldn't even start otherwise. See emscripten-core/emsdk#140
@juj

Note that we currently do not link to an installer for windows

The NSIS installer .exes on Windows were deprecated at some point, since it was not much gain to support an extra deployment workflow, and the Windows emsdk portable zip based package does much of the same thing with less hassle. The only thing that's different in the Windows emsdk portable zip package compared to macOS and Linux is that in the Windows package, we bundle portable Python 2.7.13.1 into the zip package.

@kripken

Oh hmm, I now see that the Downloads page at http://kripken.github.io/emscripten-site/docs/getting_started/downloads.html# no longer mentions a link to the downloadable zip packages. That is, to these zip files:

and indeed, in the above, emsdk-portable.zip still has old Python. I think we need to make the S3 bots roll out a new emsdk-portable zip and tar.gz packages. @kripken : that is done in the Buildbot dashboard by manually launching the emsdk-win-updater, emsdk-osx-updater and emsdk-linux-updater build tasks. Those tasks run deploy_emsdk.py to zip up and upload a emsdk-portables for download.

I was not able to find the link to the Buildbot dashboard in my email inbox, could you link to that here?

@juj

@juj do you mean this link? http://ec2-54-213-252-128.us-west-2.compute.amazonaws.com:8112/#/

I opened a PR on the emsdk repo to update the links there (to point to the website downloads docs), emscripten-core/emsdk#141

Just to add: I updated from Python 2.7.10 to 2.7.14 on macOS Sierra, and suddenly it fixed this issue. I updated with Macports:

# install latest
sudo port install python27

# alias to 'python' command
sudo port select --set python python27

Quit and re-open terminal, then run python --version to ensure it's been updated.

Just curious: It's been a while since the documentation was changed requiring windows users to install python separately from emsdk (#6298). Is this now the official norm or still just a work around until bundling python into emsdk gets resolved? We haven't changed our CI yet to install python and don't want to put in the time if in a few weeks/months it's not going to matter.

There are no current plans to improve the windows SDK install and bundle things like python - I'd love for us to, but unless someone volunteers, for now the best we can do is an experience similar to the other platforms.

In MacOS
$ /Applications/Python\ 2.7/Install\ Certificates.command
This is work

ref:https://stackoverflow.com/questions/27835619/urllib-and-ssl-certificate-verify-failed-error

Firstly,I typed "emsdk install latest" in git cmd，but it said "bash:git:command not found"
and then I got the issue code look like #6723 when i typed "./emsdk install latest" on Windows10.
Finally,I set the system path point to emsdk dir and typed "emsdk install latest" again.
It worked!!Silly me. By the way,my python version is 2.7.15.

python ./emsdk install latest works for me. I installed the newer python 2.7.16, but without typing python at the beginning, it doesn't work.

MacOS 10.14.5. Installed python from python.org.

This worked for me (OSX huge headache)
https://stackoverflow.com/questions/42098126/mac-osx-python-ssl-sslerror-ssl-certificate-verify-failed-certificate-verify

python ./emsdk install latest works for me. I installed the newer python 2.7.16, but without typing python at the beginning, it doesn't work.

MacOS 10.14.5. Installed python from python.org.

it works for me (OSX)

Here is a bandage (not secure as you bypass cert checks) to fix it:

edit emsdk.py

change
u = urlopen(url)
to
ncontext = ssl.SSLContext()
u = urlopen(url, context=ncontext)

Make sure to add:
import ssl

Here is a bandage (not secure as you bypass cert checks) to fix it:

edit emsdk.py

change
u = urlopen(url)
to
ncontext = ssl.SSLContext()
u = urlopen(url, context=ncontext)

Make sure to add:
import ssl

This results in:

N:\Web\site\harmony-dev\wasm\emsdk>emsdk install latest
Traceback (most recent call last):
  File "N:\Web\site\harmony-dev\wasm\emsdk\emsdk.py", line 25, in <module>
    import ssl
  File "C:\Users\Rualark\Anaconda3\lib\ssl.py", line 98, in <module>
    import _ssl             # if we can't import it, let the error propagate
ImportError: DLL load failed: The specified module could not be found.

Tried to install ssl:

Navigation Menu

Repository navigation

emsdk install failing #6275

32 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

emsdk install failing #6275

Description

Activity

frittblas commented on Feb 24, 2018

jjyyxx commented on Feb 25, 2018

LMLB commented on Feb 25, 2018

Krelborn commented on Feb 25, 2018

jjyyxx commented on Feb 25, 2018

LMLB commented on Feb 25, 2018

kripken commented on Feb 25, 2018

Krelborn commented on Feb 25, 2018

kripken commented on Feb 25, 2018

Krelborn commented on Feb 25, 2018

mapsam commented on Feb 25, 2018

frittblas commented on Feb 25, 2018

LMLB commented on Feb 25, 2018

Krelborn commented on Feb 26, 2018

32 remaining items

damu commented on Apr 24, 2018

juj commented on Apr 27, 2018

juj commented on Apr 27, 2018

kripken commented on Apr 27, 2018

mattdesl commented on May 20, 2018

k2snowman69 commented on Sep 8, 2018

kripken commented on Sep 11, 2018

mason276752 commented on Nov 2, 2018

zhyonc commented on Nov 29, 2018

gaopinghuang0 commented on Jul 4, 2019

F1r3Hydr4nt commented on Aug 2, 2019

UZIhuhuhu commented on Aug 2, 2019

navidmo commented on Sep 27, 2019

rualark commented on Jan 24, 2020

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions