Your logs are filling up with ECONNRESET. What's actually going on down at the socket, and how do you tell a real problem apart from noise?
A strong answer reads socket errors as protocol events, knows which side sent the RST, what half-open means, and treats ECONNRESET as having a cause.
ECONNRESET means the connection got reset by the other side, so the peer sent a TCP RST instead of closing cleanly. You see it a lot when a client disconnects before the server finishes responding, or when a timeout closes a connection, or a proxy drops an idle one. The way you handle it is attaching an error listener to the socket or the request, so an unhandled error doesn't crash the process. A half-open connection is when one side has closed its end but the other hasn't, so data can still flow one way. And the listen backlog is the queue of pending connections waiting to be accepted, if that fills up new connections can get refused. In practice you log these errors, figure out whether they point at a real client problem, and try not to treat every reset as fatal, since some of them are basically just clients going away.