ECONNRESET — connection reset by peer
The other end sent a TCP reset instead of closing cleanly. In scraping it is frequently a deliberate drop rather than a fault — some anti-bot layers reset instead of returning a status you could read.
A proxy fixes part of this. A reset from a flaky exit is fixed by retrying elsewhere. A reset that is really a block is fixed the same way as a 403, and the tell is whether it happens every time or only sometimes.
Why it happens
The target reset the connection on purpose, as a block that costs it less than serving an error page.
A residential exit disconnected mid-request.
Keep-alive reuse of a connection the far end had already closed.
A TLS handshake rejected at the transport level rather than with an alert.
How to fix it
- Retry with a fresh connection; do not reuse the socket that failed.
- Disable keep-alive if resets cluster on the second and later requests of a connection.
- If resets are immediate and consistent for one target, treat it as a block and change the fingerprint and the pool.
FAQ
What does ECONNRESET mean?›
Why am I getting ECONNRESET?›
How do I fix ECONNRESET?›
Will a proxy fix ECONNRESET?›
Other errors
Stop getting ECONNRESET
Residential IPs across 199 countries, from $7.35/GB — no commitment, no monthly plan.
Get residential IPs →