Skip to main content

How To Stop SSH Session From Disconnecting In Linux

My SSH session is closed after few minutes of inactivity, how can I prevent this?” It’s easy! As you might know already, SSH sessions will be terminated after 10 minutes of inactivity for security reasons. So, it prevents other users to access your server in case you left it connected by mistake. However, you can change this if you want to. Here is a simple solution to stop SSH session from disconnecting automatically in Linux. This method will work on most Linux systems.

Stop SSH Session From Disconnecting In Linux

The following steps needs to be performed in your SSH client, not in the remote server.

To configure the current user, edit SSH config file:

$ nano ~/.ssh/config

Add the following lines:

Host *
 ServerAliveInterval 60

Please ensure that you indent the second line with a space.

Let me explain what these lines do. Once you added these lines in your SSH client system, it will send a packet called no-op (No Operation) to your Remote system. The no-op packet will inform the remote system “Nothing to do”. Also it tells the SSH client is still connected with the remote system, hence do not close the TCP connection and log you out.

Here “Host *” indicates this configuration is applicable for all remote hosts. “ServerAliveInterval 60” indicates the number of seconds to wait to send a no-op packet.

To configure this to particular host, you need add the remote host’s name after “Host” line as shown like below.

Host ostechnix
 ServerAliveInterval 60

The above configuration only prevents the SSH session of a remote host called “ostechnix” from being disconnected.

Run the following command to apply the settings.

$ source ~/.ssh/config

To apply this settings for all users (globally) in your system, add or modify the following line in /etc/ssh/ssh_config file.

ServerAliveInterval 60

Save and close the file.

Now the SSH session will not terminate after a particular period of time.


Comments

Post a Comment

Popular posts from this blog

4 Ways to Communicate Across Browser Tabs in Realtime

1. Local Storage Events You might have already used LocalStorage, which is accessible across Tabs within the same application origin. But do you know that it also supports events? You can use this feature to communicate across Browser Tabs, where other Tabs will receive the event once the storage is updated. For example, let’s say in one Tab, we execute the following JavaScript code. window.localStorage.setItem("loggedIn", "true"); The other Tabs which listen to the event will receive it, as shown below. window.addEventListener('storage', (event) => { if (event.storageArea != localStorage) return; if (event.key === 'loggedIn') { // Do something with event.newValue } }); 2. Broadcast Channel API The Broadcast Channel API allows communication between Tabs, Windows, Frames, Iframes, and  Web Workers . One Tab can create and post to a channel as follows. const channel = new BroadcastChannel('app-data'); channel.postMessage(data); And oth...
Post a Comment
Read more

Certbot SSL configuration in ubuntu

  Introduction Let’s Encrypt is a Certificate Authority (CA) that provides an easy way to obtain and install free  TLS/SSL certificates , thereby enabling encrypted HTTPS on web servers. It simplifies the process by providing a software client, Certbot, that attempts to automate most (if not all) of the required steps. Currently, the entire process of obtaining and installing a certificate is fully automated on both Apache and Nginx. In this tutorial, you will use Certbot to obtain a free SSL certificate for Apache on Ubuntu 18.04 and set up your certificate to renew automatically. This tutorial will use a separate Apache virtual host file instead of the default configuration file.  We recommend  creating new Apache virtual host files for each domain because it helps to avoid common mistakes and maintains the default files as a fallback configuration. Prerequisites To follow this tutorial, you will need: One Ubuntu 18.04 server set up by following this  initial ...
Post a Comment
Read more

Working with Node.js streams

  Introduction Streams are one of the major features that most Node.js applications rely on, especially when handling HTTP requests, reading/writing files, and making socket communications. Streams are very predictable since we can always expect data, error, and end events when using streams. This article will teach Node developers how to use streams to efficiently handle large amounts of data. This is a typical real-world challenge faced by Node developers when they have to deal with a large data source, and it may not be feasible to process this data all at once. This article will cover the following topics: Types of streams When to adopt Node.js streams Batching Composing streams in Node.js Transforming data with transform streams Piping streams Error handling Node.js streams Types of streams The following are four main types of streams in Node.js: Readable streams: The readable stream is responsible for reading data from a source file Writable streams: The writable stream is re...
Post a Comment
Read more