Cloning repository error: This is not a valid source path/ URL (Mac OSX, SourceTree 2.4)

[Andre dos Santos]

Hello everyone,

I have been trying to clone a repository created with the C4Science service, without any success. Whenever I input the URL, either the https or ssh, I get the error: "this is not a valid source path/URL". The https log shows up empty, while the latter yields the following: 

"fatal: 'git@c4science....' does not appear to be a git repository

fatal: Could not read from remote repository."

I have tried using the system Git (version 2.10), then resetting to the embedded one (2.8). I have linked my GitHub, Atlassian and C4Science accounts (perhaps there was an authorization issue). I have tried a clean install of all SourceTree, Git, mercurial, even updated Python (for Mercurial). I have also tried deleting my SourceTree Library files in order to reinitialise the first set up wizard, to no avail. 

My colleagues managed to clone the repository from a fresh install with no issue, following the exact same installations steps as given in the documentation. Also note that we all skipped the original BitBucket/GitHub login step during setup. Is there something I am missing? Any help with this issue would be appreciated.

More info:

SourceTree V 2.4

OSX El Capitan V 10.11.6

EDIT: Solved! I just had to install version 2.3 of SourceTree and it worked immediately.

[Eskil Gjerde Sviggum]

I had the same issue!

You have to open up preferences(cmd+,) then go to the accounts tab and click on the account you want to use, then click "Edit" and locate where it says Protocol if that is set to SSH you have to change it to HTTPS.

That fixed the issue for me.

[Phil Bergner]

This was already set for me, didn't solve the issue unfortunately.

[Andre dos Santos]

That unfortunately didn't work for me when I tried it.

What solved it in the end was giving up on Version 2.4 and installing 2.3 instead. It worked instantly with the previous version.

Hope that helped!

[Cody Swartz]

This seems to be broken for me as well with version 2.4 on mac
I tried to swap the account to default and to https but had no luck, I'm still getting the same error. 

[Hammad Ahmed]

Switch to authentication mode from OAuth to Basic. It will work!

[Ligia Franco]

Thanks! That fixed the issue for me.

[Theerapat Kijpramuan]

preferences > accounts > edit > oauth to Basic 

and SSH to HTTPS 

fixed this for me!

[Jose Capistrano]

This fixed the issue for me!

[Daniel Rammer]

Updating your embedded Git might also fix the issue.

[Phil Bergner]

@Andre dos Santos were you ever able to resolve this?

[Chien-Tai Cheng]

I face the same issue, I will try 2.3. What's wrong with 2.4 ??? 

[Hua Duong Nguyen]

I have the same issue with v2.4 and now I'm trying to downgrade to 2.3 where everything worked just fine..

[Cody Swartz]

How do I downgrade to v2.3? I cannot seem to find a download link, I found a list for Windows, but nothing for Mac yet.

[Yaty Lee]

chmod 600 ~/.ssh/id_rsa

[Sashi Bala]

Had similar issue on version 2.4.8. I installed git on the machine and it worked after that. You could do this by going to Source Tree --> Tools --> Options --> Git -->Use Embedded git (If you haven't installed git on your machine) or Use System Git (If you have installed git on your machine.)

[Jay Collier]

Same problem with Sourcetree Mac 2.7.1. Using locally-installed or embedded results in same error.

[Gabriel Michels]

Alright, so I just ran into this problem (once again). Same as Jay neither embedded nor local git would make a difference.
On this note: I let sourcetree create a SSH key and add it to my github on my behalf. It was listed, my ssh agent would list the key. Was looking all good, but it would still fail to clone.

What solved it in the end was deleting the ssh key from my github and adding it manually again.

Now it works fine.

[Ted Toal]

For me, the problem was this: I generated a key using Sourcetree.  It named the file that contained the key with a SPACE in the filename (it ended with " -Bitbucket".  That space messed up its own ability to find the key file.  I solved it by editing the file ~/.ssh/config and putting double-quote marks around the filename:  "xxxx -Bitbucket"    It then worked!!!!