Member-only story
How do I debug error ECONNRESET in Node.js?
You might have guessed it already: it’s a connection error.
“ECONNRESET” means the other side of the TCP conversation abruptly closed its end of the connection. This is most probably due to one or more application protocol errors. You could look at the API server logs to see if it complains about something.
But since you are also looking for a way to check the error and potentially debug the problem, you should take a look at “How to debug a socket hang up error in NodeJS?” which was posted at stackoverflow in relation to an alike question.
Quick and dirty solution for development:
Use longjohn, you get long stack traces that will contain the async operations.
Clean and correct solution: Technically, in node, whenever you emit an
'error'
event and no one listens to it, it will throw. To make it not throw, put a listener on it and handle it yourself. That way you can log the error with more information.To have one listener for a group of calls you can use domains and also catch other errors on runtime. Make sure each async operation related to http(Server/Client) is in different domain context comparing to the other parts of the code, the domain will automatically listen to the
error
events and will propagate it to it's own handler. So you only listen to that handler and get the error data. You also get more information for free.