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

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.

 

11 answers

This widget could not be displayed.

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.

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

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!

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. 

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

Thanks! That fixed the issue for me.

preferences > accounts > edit > oauth to Basic 

and SSH to HTTPS 

fixed this for me!

This fixed the issue for me!

This widget could not be displayed.

Updating your embedded Git might also fix the issue.

This widget could not be displayed.

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

This widget could not be displayed.

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

This widget could not be displayed.

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

This widget could not be displayed.

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.

This widget could not be displayed.
Yaty Lee I'm New Here Apr 03, 2018

chmod 600 ~/.ssh/id_rsa

This widget could not be displayed.

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.)

This widget could not be displayed.

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

This widget could not be displayed.

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.

This widget could not be displayed.
Ted Toal I'm New Here Aug 09, 2018

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!!!!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published May 30, 2018 in Sourcetree

Tip from the team: configuring Git or Mercurial in Sourcetree

Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...

860 views 2 3
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you