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

events.js:163 throw er; // Unhandled 'error' event... Node Version v7.10.0 #18124

Closed
rsmodake opened this issue Jan 12, 2018 · 4 comments
Closed
Labels
question Issues that look for answers. wrong repo Issues that should be opened in another repository.

Comments

@rsmodake
Copy link

rsmodake commented Jan 12, 2018

Hi All,

I have installed protractor on my machine. When I fire below command,
webdriver-manager update
I get below error,

events.js:163
throw er; // Unhandled 'error' event
^

Error: tunneling socket could not be established, statusCode=407
at ClientRequest.onConnect (/usr/local/lib/node_modules/protractor/node_modules/tunnel-agent/index.js:166:19)
at Object.onceWrapper (events.js:293:19)
at emitThree (events.js:116:13)
at ClientRequest.emit (events.js:197:7)
at Socket.socketOnData (_http_client.js:443:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at readableAddChunk (_stream_readable.js:178:18)
at Socket.Readable.push (_stream_readable.js:136:10)
at TCP.onread (net.js:561:20)

I am using node version V7.10.0

Please help me to resolve the issue. My colleague is having same version, but he is not facing any issues.

@profnandaa
Copy link
Contributor

@rsmodake - can post this on https://github.com/nodejs/help ?

@bnoordhuis bnoordhuis added question Issues that look for answers. wrong repo Issues that should be opened in another repository. labels Jan 12, 2018
@bnoordhuis
Copy link
Member

Also keep in mind that node.js v7.x is out of support.

@Ar3sion
Copy link

Ar3sion commented Oct 30, 2018

This sounds like another instance of node is already running a socket on the same port...

@srafik-jd
Copy link

srafik-jd commented Nov 14, 2018

This sounds like another instance of node is already running a socket on the same port...

Life Saver! Thanks a ton

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Issues that look for answers. wrong repo Issues that should be opened in another repository.
Projects
None yet
Development

No branches or pull requests

5 participants