#Termius digitalocean how to

Method 1: Client side SSH configuration change If you are a sysadmin and several of users complain about frequent SSH connection disconnect, you may set it on the server.If you connect to multiple servers via SSH, set it on your machine.Either you send the alive message from the client to the server or from the server to the client. This way, you keep the SSH session alive because there is a communication between the client and server and the server understands that client is still there. What you can do to avoid the SSH session disconnection is to send an 'alive message' either from the server to client ( ClientAliveInterval) or from client to server ( ServerAliveInterval) at certain time interval. There is no set value but it usually around 5 minutes or so. Fixing broken pipe error with SSHĪs you may have guessed, the SSH connection is closed because of inactivity.

#Termius digitalocean how to

Let's see what causes this error and how to go about keeping your SSH connection alive. On some systems, it will display 'Write failed: Broken pipe' or 'Connection closed by remote host'. If you use SSH to connect to remote Linux servers, you'll notice that if you keep your SSH session inactive for some time and then try to use it again, the SSH session disconnects with an error message like this: :client_loop: send disconnect: Broken pipe