Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CERT Errors - and ECONNREFUSED #78

Open
brian-lamb-software-engineer opened this issue Oct 13, 2017 · 0 comments
Open

CERT Errors - and ECONNREFUSED #78

brian-lamb-software-engineer opened this issue Oct 13, 2017 · 0 comments

Comments

@brian-lamb-software-engineer
Copy link

brian-lamb-software-engineer commented Oct 13, 2017

Im running a windows box using msys2 (mingw64 based) terminals. Node is installed on the windows box. I have set my config to use an alt port because it clashes with xampp. The port is the only thing adjusted on the init'ed config file (in both places, the port and the url)

When i run npm install, it looks successful, probably because I wasn't having this problem a couple days ago when i installed npm_lazy and configured it, but ive done something to mess it up possibly, or the corp network isnt allowing the TLS auth maybe, see below..

Im getting Cert issues when i try to run npm update, see an example of what i see(one of hundreds) from the output in npm_lazy terminal ran from my alt config.

app debug Fetch failed (3/5): https://registry.npmjs.com/punycode { Error: unable to get local issuer certificate
    at Error (native)
    at TLSSocket.<anonymous> (_tls_wrap.js:1092:38)
    at emitNone (events.js:86:13)
    at TLSSocket.emit (events.js:185:7)
    at TLSSocket._finishInit (_tls_wrap.js:610:8)
    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:440:38)
  code: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY',
  contentStream: undefined }
app debug [GET] https://registry.npmjs.com/punycode

This ended in failure after what seemed thousands of the cert errors above, one for each package it apeared.

Here was the output for the npm update terminal.

$ npm update
npm WARN deprecated [email protected]: jvectormap is not maintened since Aug 2015. You can use jvectormap-next or jqvmap instead.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\url\node_modules\querystring):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Error: connect ECONNREFUSED 127.0.0.1:8079
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "update"
npm ERR! node v6.11.0
npm ERR! npm  v3.10.10
npm ERR! code ECONNREFUSED
npm ERR! errno ECONNREFUSED
npm ERR! syscall connect

npm ERR! Error: connect ECONNREFUSED 127.0.0.1:8079
npm ERR!     at Object.exports._errnoException (util.js:1018:11)
npm ERR!     at exports._exceptionWithHostPort (util.js:1041:20)
npm ERR!     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)
npm ERR!  { Error: connect ECONNREFUSED 127.0.0.1:8079
npm ERR!     at Object.exports._errnoException (util.js:1018:11)
npm ERR!     at exports._exceptionWithHostPort (util.js:1041:20)
npm ERR!     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)
npm ERR!   code: 'ECONNREFUSED',
npm ERR!   errno: 'ECONNREFUSED',
npm ERR!   syscall: 'connect',
npm ERR!   address: '127.0.0.1',
npm ERR!   port: 8079,
npm ERR!   parent: 'url' }
npm ERR!
npm ERR! If you are behind a proxy, please make sure that the
npm ERR! 'proxy' config is set properly.  See: 'npm help config'

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

No branches or pull requests

1 participant