Error AtlasError Documentation and Resolution
Back to searchMore Node.js errors

Node.js

Node.js connection was reset by the peer

ECONNRESET: connection reset by peer

Node.js was communicating over a socket, but the remote side closed the connection unexpectedly before the exchange completed.

ECONNRESETnetwork

Observed message

ECONNRESET: connection reset by peer

Why it happens

  • The remote server timed out, restarted, or closed the connection abruptly.
  • A proxy or intermediary terminated the socket before the response completed.
  • The client or server wrote to a socket that was already being closed.

How to fix it

  1. Check whether the remote service is timing out or restarting during requests.
  2. Review proxy and load balancer timeout settings between the client and server.
  3. Add retry or graceful error handling where transient connection resets are expected.

Official reference

Node.js Errors

Related errors

ECONNREFUSEDNode.js connection was refused by the target serviceEADDRINUSENode.js could not bind because the address is already in useETIMEDOUTNode.js operation timed out before completionENOENTNode.js could not find the requested file or directory

Explore more

Node.jsBrowse more Node.js errorsnetworkBrowse more network errors
Node.js ECONNRESET connection reset by peer: causes and fixes | Error Atlas