Problem Definition

In the event that ServerAliveInterval is not set in the ssh config of a user, 10 minutes is the maximum time that a SSH session can be alive. This can mean that if a user is performing long running Git LFS transfers, that the SSH session will be killed during the upload of LFS files.

Suggested Solution

Bitbucket Server could be able to sent keep alive packets to ensure that the ssh session was kept alive without the client having to set up their own keep alive settings.

Workaround

Set ServerAliveInterval to a value that is lower than 10 minutes in the relevant config file for your system (~/.ssh/config for OpenSsh systems). If your Bitbucket instance is behind a load balancer, you'll need to set ServerAliveInterval to less than 10 minutes, or your load balancers' idle timeout. Whichever is lower.

Note: If using SourceTree, you must change your SSH agent from PuTTY to OpenSSH in order to successfully apply this configuration. You can do this by going to Tools >> Options and selecting the SSH agent. You will also need to make sure your SSH keys are in the correct format for OpenSSH, e.g. with an id_rsa file.