K
K
komarevtsev2016-06-11 12:26:21
Node.js
komarevtsev, 2016-06-11 12:26:21

Getting a node js error?

I 'm working on a local computer. An
error occurs quite randomly:
events.js: 141
throw er; // Unhandled 'error' event
^
Error: socket hang up
at createHangUpError (_http_client.js:203:15)
at Socket.socketOnEnd (_http_client.js:288:23)
at emitNone (events.js:72:20)
at Socket .emit (events.js:166:7)
at endReadableNT (_stream_readable.js:905:12)
at doNTCallback2 (node.js:441:9)
at process._tickCallback (node.js:355:17)
Maybe someone did you encounter?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
Y
yurii_12345, 2016-12-22
@yurii_12345

The port you are accessing is currently occupied by another application.
Check whether any other Terminal is running other Applications on the same port. This happens when multiple applications trying to access the same port, Its always FIFO.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question