One of the things you should do when first setting up your new server is changing the SSH port. This is not because it will actually stop a real attacker but because your server will be hammered with automated random login attempts, so the real reason why we will change the default ssh port is so that when the automated attacks can’t even connect to port 22 then usually it just stops and moves on to the next server. If you are using a cloud droplet or VPS that supports snapshots, now is the time to take one just incase you get locked out if something goes terribly wrong (never hurts to be safe!).
If you get even remotely as annoyed as I do when you recieve an SSH timeout or disconnect then this post is for you. Below is how to quickly and easily fix the SSH timeout issue on the server side. This solution will not disable the timeouts entirely though, instead it just sets the threshold extremely high. While you can fix ssh timeouts on your clients, its much better to do so on your server that way you won’t have to do it on every single client/computer that is used to connect to your server.