◆Error Codes Wiki

Linux Error ECONNRESET (errno 104) — Connection Reset Fix

Warninglinux errno

About Linux Error ECONNRESET (errno 104)

Linux errno 104 ECONNRESET means the connection was forcibly closed by the remote host. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: Error: ECONNRESET (errno 104). Message: Connection reset by peer. Remote end abruptly closed the connection. Data may have been lost in transit. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: Remote server crashed or restarted. Load balancer idle timeout reached. Client sent data after server closed connection. Firewall killed the connection. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Implement connection retry logic. Check remote server health and logs. Increase keep-alive timeouts. Use connection pooling with health checks. Check for load balancer timeout settings. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our Linux Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.

Quick Answer

Is this a client or server issue?

Usually server-side — the remote end reset the connection.

Overview

Linux errno 104 ECONNRESET means the connection was forcibly closed by the remote host.

Key Details

  • Error: ECONNRESET (errno 104)
  • Message: Connection reset by peer
  • Remote end abruptly closed the connection
  • Data may have been lost in transit

Common Causes

  • Remote server crashed or restarted
  • Load balancer idle timeout reached
  • Client sent data after server closed connection
  • Firewall killed the connection

Steps

  1. 1Implement connection retry logic
  2. 2Check remote server health and logs
  3. 3Increase keep-alive timeouts
  4. 4Use connection pooling with health checks
  5. 5Check for load balancer timeout settings

Tags

linuxlinux-errnolinux errno 104ubuntuterminal

More in Linux Errno

linux-errno-28Linux Error ENOSPC (errno 28) — No Space Left on Device Fix
Critical
linux-errno-111Linux Error ECONNREFUSED (errno 111) Fix
Critical
linux-errno-110Linux Error ETIMEDOUT (errno 110) — Connection Timed Out Fix
Critical
linux-errno-24Linux Error EMFILE (errno 24) — Too Many Open Files Fix
Critical
linux-errno-14Linux Error EFAULT (errno 14) — Bad Address Fix
Warning

Frequently Asked Questions

Usually server-side — the remote end reset the connection.