A while ago, I had this error on BitBucket:
Running git.exe with arguments "fetch --prune" failed with return code 128 and error output: "fatal: unable to access 'https://%account%@bitbucket.org/%user%/%repository%.git/': Unknown SSL protocol error in connection to bitbucket.org:443
A quick search for “Unknown SSL protocol error in connection to bitbucket.org:443” pointed me to a comment by Ludwik Trammer on an answer by Jordfräs:
I resolved the issue by upgrading from git 1.8 to git 2.0.
Which reminded me this was a Windows system, where there is no package manager that verifies how far your non-system software is behind.
One day, I will write a script that finds out about the git version history and inform me of major/minor versions I’ve skipped.
Some notes for that:
- This VM was at “git version 1.8.5.2.msysgit.0” from indeed a very old “Git-1.8.5.2-preview20131230.exe”.
- For version 1.x, the Windows development of Git
- was at the repository https://github.com/msysgit/msysgit
- release history was at https://github.com/msysgit/msysgit/releases.
- Now I’m at “git version 2.6.1.windows.1” from “Git-2.6.1-32-bit.exe” from https://github.com/git-for-windows/git/releases/latest.
- For version 2.0+, the Windows development Git
- is at the repository https://github.com/git-for-windows/git
- release history is at https://github.com/git-for-windows/git/releases.
- the latest download is at https://git-scm.com/download/win which will auto-download the 32-bit version and provides manual downloads of the x64 version.
Probably I will need to do something similar for Mercurial/hg in the future as well.
–jeroen
via: git – Unknown SSL protocol error in connection – Stack Overflow
Filed under: Development, DVCS - Distributed Version Control, git, Power User, Software Development, Source Code Management, Windows, Windows 7, Windows 8, Windows 8.1, Windows 9, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
