Comments on: How to Fix SSH Client_loop: send disconnect: Broken pipe Error

By: Ravi Saive

Ravi Saive — Mon, 19 May 2025 04:53:11 +0000

In reply to Gudrun.

@Gudrun,

SSH has always used sockets (specifically TCP sockets), so that’s not new. It’s more likely that your update changed how idle connections are handled, possibly due to OpenSSH, systemd, or firewall updates.

By: Gudrun

Gudrun — Sat, 17 May 2025 11:14:04 +0000

In reply to Wastrel.

is this maybe because SSH uses sockets now?

By: Ray Kooyenga

Ray Kooyenga — Sat, 14 Dec 2024 05:36:33 +0000

In reply to Supritam.

Hey fellas, I’ve had this issue come up too. Changing some of the values client-side even made it worse, and I started getting logged out every couple of minutes.

Here’s what I did to solve it.

The difference was made by these values in sshd_config:

Remote sshd_config:

TCPKeepAlive yes  
ClientAliveInterval 60  
ClientAliveCountMax 3

Local ssh/config:

Host *  
    ServerAliveInterval 2000  
    TCPKeepAlive yes  
    ServerAliveCountMax 3  
    Compression yes

Ubuntu 22.04 servers, ChromeOS/Ubuntu local.

By: Supritam

Supritam — Mon, 28 Oct 2024 09:11:19 +0000

Still, my issue is not resolved. The same error occurs even after entering the same details.

By: Peter

Peter — Mon, 05 Aug 2024 16:53:39 +0000

In reply to Wastrel. Good question. “TCPKeepAlive yes” in the config file solved my problem. I've got the "client_loop: send disconnect: Broken pipe" message each time I rebooted the remote server after an upgrade to Ubuntu 24.04. “TCPKeepAlive yes” in the config file brought back the former behaviour. Of course, this was not a big issue, but a little bit annoying, because I expected something wrong in my network setup that could negatively affect other users.