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!
Accepted Answer
@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 ~/.ssh/config file:
Host *
ServerAliveInterval 240
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 600.
On the other hand you can use tmux which keeps your session alive and enables you to go back for it even after the ssh connection is closed.
Hope this helps.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.