Unable to push repository with Windows Server 2008R2 using TLS1

[tdooling]

When trying to push a repository to the remote I get the following response:

git.exe push --all --force --progress "origin"

error: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure while accessing https://tdooling@bitbucket.org/cccit/adm.git/info/refs?service=git-receive-pack
fatal: HTTP request failed

git did not exit cleanly (exit code 128) (703 ms @ 3/21/2019 9:06:57 AM)

Our system is Windows Server 2008R2.  It currently only supports TLS1.

We are running TortoiseGit 1.8.7.0 with git version 1.8.1.msysgit.1.  I know the problem is that bitbucket no longer supports TLS1 ro TLS1.1.  See https://bitbucket.org/blog/deprecating-tlsv1-tlsv1-1-2018-12-01?_ga=2.135284209.130327637.1553176885-1108313655.1531245680.

Upgrading our server to TLS1.2 is not an option at this point because we are deprecating the server itself, but I want to be able to transfer the applications to the repository before we abandon the server.

What do we need to do to upgrade our git, if possible, to be able to connect to the remote server?

[Daniel Eads · Accepted solution]

Hey Timothy,

You might have already read the blog post describing our deprecation of TLS 1.0 and 1.1. Since there are so many possible clients that might be out of date, we couldn't provide specific info about upgrading in the blog post.

It looks like TortoiseGit doesn't bundle the actual git library as part of its build. Your steps to get upgraded will look like this:

1. Upgrade TortoiseGit to the latest release - notes and a download link on their FAQ
2. Upgrade to the latest git CLI - separate download from the git website

Git for Windows v2.16 was the first to support TLS 1.2. The latest release as of today is 2.21 - just adding this info here if you are looking for "what version do I need to at least upgrade to if I don't want to go all the way to the latest release".

Hope that helps!
Daniel

[tdooling]

Thanks.

I was able to get it working again by upgrading to the latest version of Git first, and then upgrading to TortoiseGit 2.4.

The TortoiseGit installer views our installation of Windows Server2008R2  as Windows Vista.  That was the main problem preventing upgrade of TortoiseGit, but the communications problem needed an upgrade of Git to work.