Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

SSL protocol issue #5786

Closed
vladovidiu opened this Issue Jul 24, 2014 · 4 comments

Comments

Projects
None yet
3 participants

Hey guys, I am using the latest version of node. Here is the full log:

0 info it worked if it ends with ok
1 verbose cli [ 'E:\Tools\nodejs\node.exe',
1 verbose cli 'E:\Tools\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'install',
1 verbose cli '-g',
1 verbose cli 'express-generator' ]
2 info using npm@1.4.14
3 info using node@v0.10.29
4 verbose node symlink E:\Tools\nodejs\node.exe
5 verbose cache add [ 'express-generator', null ]
6 verbose cache add name=undefined spec="express-generator" args=["express-generator",null]
7 verbose parsed url { protocol: null,
7 verbose parsed url slashes: null,
7 verbose parsed url auth: null,
7 verbose parsed url host: null,
7 verbose parsed url port: null,
7 verbose parsed url hostname: null,
7 verbose parsed url hash: null,
7 verbose parsed url search: null,
7 verbose parsed url query: null,
7 verbose parsed url pathname: 'express-generator',
7 verbose parsed url path: 'express-generator',
7 verbose parsed url href: 'express-generator' }
8 silly lockFile 198a68d8-express-generator express-generator
9 verbose lock express-generator C:\Users\vtutunea\AppData\Roaming\npm-cache\198a68d8-express-generator.lock
10 silly lockFile 198a68d8-express-generator express-generator
11 silly lockFile 198a68d8-express-generator express-generator
12 verbose addNamed [ 'express-generator', '' ]
13 verbose addNamed [ null, '' ]
14 silly lockFile bd41e3d3-express-generator express-generator@
15 verbose lock express-generator@ C:\Users\vtutunea\AppData\Roaming\npm-cache\bd41e3d3-express-generator.lock
16 silly addNameRange { name: 'express-generator', range: '
', hasData: false }
17 verbose url raw express-generator
18 verbose url resolving [ 'https://registry.npmjs.org/', './express-generator' ]
19 verbose url resolved https://registry.npmjs.org/express-generator
20 info trying registry request attempt 1 at 09:57:43
21 http GET https://registry.npmjs.org/express-generator
22 info retry will retry, error on last attempt: Error: 2248:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:openssl\ssl\s23_clnt.c:787:
23 info trying registry request attempt 2 at 09:57:53
24 http GET https://registry.npmjs.org/express-generator
25 info retry will retry, error on last attempt: Error: 2248:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:openssl\ssl\s23_clnt.c:787:
26 info trying registry request attempt 3 at 09:58:53
27 http GET https://registry.npmjs.org/express-generator
28 silly lockFile bd41e3d3-express-generator express-generator@
29 silly lockFile bd41e3d3-express-generator express-generator@
30 error Error: 2248:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:openssl\ssl\s23_clnt.c:787:
30 error
30 error at SlabBuffer.use (tls.js:232:18)
30 error at CleartextStream.read as _read
30 error at CleartextStream.Readable.read (_stream_readable.js:323:10)
30 error at EncryptedStream.write as _write
30 error at doWrite (_stream_writable.js:226:10)
30 error at writeOrBuffer (_stream_writable.js:216:5)
30 error at EncryptedStream.Writable.write (_stream_writable.js:183:11)
30 error at write (_stream_readable.js:585:24)
30 error at flow (_stream_readable.js:594:7)
30 error at Socket.pipeOnReadable (_stream_readable.js:626:5)
30 error at Socket.emit (events.js:92:17)
31 error If you need help, you may report this entire log,
31 error including the npm and node versions, at:
31 error http://github.com/npm/npm/issues
32 error System Windows_NT 6.1.7601
33 error command "E:\Tools\nodejs\node.exe" "E:\Tools\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "express-generator"
34 error cwd E:
35 error node -v v0.10.29
36 error npm -v 1.4.14
37 verbose exit [ 1, true ]

@othiym23 othiym23 added the support label Jul 24, 2014

Contributor

othiym23 commented Jul 24, 2014

It looks like there may be some kind of proxy sitting between your machine and the registry. Do you have to use a proxy to browse the web?

Member

KenanY commented Nov 17, 2014

Hey @vladovidiu, it's been quite a few months. Are you still having this issue?

@KenanY Sorry for not replying and closing the issue, but @othiym23 was right. There was a proxy blocking that connection. Thank you.

Contributor

othiym23 commented Nov 20, 2014

Closing as resolved!

@othiym23 othiym23 closed this Nov 20, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment