n8n errors / Connectivity
read ECONNRESET
Cause
The remote server abruptly closed the TCP connection mid-transfer, often due to firewall rules, TLS mismatches, keep-alive timeouts, or the n8n host lacking a stable outbound IP on the target's allowlist.
Fix
Retry the request to rule out a transient blip, then confirm your n8n host's outbound IP is not blocked or rate-limited by the target. In Docker, ensure a stable network route (not NAT hairpin). Enable 'Retry on Fail' on the HTTP Request node (3 retries, 1s wait); for SFTP, downgrading ssh2-sftp-client to 10.x has resolved it.
Part of the Automation Error Index — n8n errors: browse all.
Hitting an automation error we have not covered?
AutomateLab builds and debugs n8n, Make, and agent workflows as fixed-scope projects. If something is broken in production, tell us what you are seeing.
Describe the problem