Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

Installation Error #13552

Closed
3 tasks
genezaretskiy opened this issue Aug 2, 2016 · 2 comments
Closed
3 tasks

Installation Error #13552

genezaretskiy opened this issue Aug 2, 2016 · 2 comments

Comments

@genezaretskiy
Copy link

genezaretskiy commented Aug 2, 2016

I'm opening this issue because:

  • npm is crashing.
  • [Y] npm is producing an incorrect install.
  • npm is doing something I don't understand.
  • Other (see below for feature requests):

What's going wrong?

How can the CLI team reproduce the problem?

I was trying to install OpenFin CLI tool and following instraction from https://openfin.co/openfin-runtime-introduction/
And have an Error.

supporting information:

  • npm -v prints: error npm v2.15.8
  • node -v prints: error node v4.4.7
  • npm config get registry prints:
  • Windows, OS X, or Linux?: Windows

31 error Windows_NT 6.1.7601
32 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "openfin-cli"
33 error node v4.4.7
34 error npm v2.15.8
35 error code EPROTO
36 error errno EPROTO
37 error syscall write
38 error write EPROTO 101057795:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:openssl\ssl\s23_clnt.c:794:

@sgregory7
Copy link

317 error Windows_NT 6.1.7601
318 error argv "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js" "install"
319 error node v6.6.0
320 error npm v3.10.3
321 error code EPROTO
322 error errno EPROTO
323 error syscall write
324 error write EPROTO 101057795:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:openssl\ssl\s23_clnt.c:794:
325 error If you need help, you may report this error at:
325 error https://github.com/npm/npm/issues

@npm-robot
Copy link

We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants