I have a dedicated server with … another web host. I can log in using SSH, start up a vim or two, fool around, rapid prototype, etc., then come back the next day (or week) and that SSH connection is still open, and my dev environment is still there.
With DO, a SSH connection to my Droplet closes after about 2-3 hours, and certainly won’t last over night.
Is there a setting somewhere to keep SSH connections open?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
@jedihawk On one hand you can configure your client to keep the connection alive by sending keep alive packets every few seconds, to do this add this line to your
Now your client will send a keep alive packet in all your ssh connections every 240 seconds, make sure the config file has the following permissions
On the other hand you can use
tmuxwhich keeps your session alive and enables you to go back for it even after the ssh connection is closed.
Hope this helps.