Software caused connection abort
Your own system aborted the connection
Seen in Linux and macOS (ECONNABORTED), Windows (WSAECONNABORTED 10053), ssh, browsers and mail clients
The connection was torn down on your side, by the local network stack or a local program, rather than reset by the server.
Common causes
- A network change (Wi-Fi drop, sleep, VPN reconnect, interface going down) killed open connections.
- A local firewall, antivirus or VPN client aborted the connection.
- The local TCP stack gave up after retransmissions went unanswered for too long.
How to fix it
- Check whether the network or VPN dropped at the time of the error, and retry.
- Temporarily disable local security software to see whether it is the cause, then add an exception.
- For long idle sessions such as SSH, enable keepalives so the path stays open.
Got a different message? Paste it into the error explainer.
Related errors
- Broken pipe · Wrote to a connection or pipe that was already closed
- Destination host unreachable. · No path to the host could be found
- TTL expired in transit. · Packets ran out of hops before arriving
- PING: transmit failed. General failure. · Windows could not send the ping at all
- Packet needs to be fragmented but DF set. · The packet is bigger than the path MTU
- ECONNREFUSED · Connection refused
- ETIMEDOUT · Connection timed out
- ECONNRESET · Connection reset by peer
- EHOSTUNREACH · No route to host
- getaddrinfo ENOTFOUND · The hostname doesn't exist in DNS
- getaddrinfo EAI_AGAIN · Temporary DNS failure
- ENETUNREACH · Network is unreachable