Although I cannot push to it the remote repository contents are visible in sourcetree so I can quite clearly read the repository (i.e. it is not a password error or similar).
When I try to push I get this message: "fatal: unable to access 'https://bitbucket.org/my/project/': error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
Pushing to https://bitbucket.org/my/project"
I have tried issuing a push command directly in the terminal window but this produces exactly the same error.
It is the same with all my projects.
I have created a dummy project and tried to upload it to bitbucket but this also does not work, the new repository is not created and the error message is the same.
Help!
If and when a yellow flag appears near the top right of the sourcetree window follow the instructions to update embedded Git. If the flag does not appear the problem is probably something else.
Hi
It is probable your are being effected by the removal of TLS 1/1.1 from Bitbucket please see https://community.atlassian.com/t5/Sourcetree-questions/Unable-to-authenticate-on-Windows-using-username-password/qaq-p/954836#M26404 for more information
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michael,
Thank you, yes that is(was) almost certainly the problem. The other recent change to sourcetree is that embedded git is no longer updated when sourcetree is updated. When I discovered this I went through the recommended procedure to update embedded git and this restored everything to working order.
Cheers... Ian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Actually, Sourcetree has never forced Git updates, something we are reviewing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michael,
Sorry for giving "fake news"! I'm afraid I read that it was a change on another forum and did not check.
Good idea to force git updates though given to security risks of using out-of-date products.
Can I also suggest, that although the alert flag is a good idea including a "check for updates" on the menus would be nice to have, too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can check in the Tools/Options/Updates tab, but it isn't the most obvious place to go and look to be fair.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.