I am trying to clone a repository, my OpenSSH is set up correctly and I can do everything fine in Git Bash. But when I put in the git@ address in SourceTree the Checking Source loading icon just spins forever and doesn't allow me to do anything.
Similarly, if I clone in Bash and then add the repo as a bookmark, Fetching the master branch also never completes and just shows the loading bar forever.
I had this problem today and spent almost all of it trying to work out what the issue is. To be clear this only occurs, for me, when using SourceTree with Bitbucket, over ssh and using Putty, not OpenSSH.
The problem appears to be that Putty has no known host for Bitbucket. Typically, Putty stores these in the registry. Despite this, SourceTree does not prompt for you to add this entry so it seems that this is a bug in SourceTree.
To get this to work, you need to connect to Bitbucket, using the same plink that is distributed with SourceTree, on the command line. This will then correctly prompt you to save Bitbucket as a known host. Afterwards, SourceTree will start working properly when you clone.
For me this involved running the following in a Windows command prompt:
cd "C:\Program Files (x86)\Atlassian\SourceTree\tools\putty"
When you are prompted to save Bitbucket as a known host, just type "yes" and then press enter.
I had the same problem, worked this out the hard way. Further confused because sometimes the putty agent can be killed with task manager and a prompt will be displayed to add the host key.
From my experience, I'd add the suggestion that it may be necessary to kill the putty agent and restart source tree.
Hello, I had the same problem "Checking Source" spins forever.
But nothing in this topic helped me. To be honest I did not understand half of the answers.
What helped me - I had a direct address link to git, for example like this:
I cut it short, leaving only port, like this:
And only after this, SourceTree asked me about key cache or whatever. And after I checked "yes", I've been able to write full direct adress to git and it accepted.
If you are using SSH and System Git, try using the embedded version of Git. Once source tree recognizes your RSA key properly you should be able to switch back to System Git.
I just ran into this problem when setting up a new machine. I was using system git and generated my RSA keys from the command line as well as a .ppk using puttygen. My keys were properly added to both Source Tree and bitbucket, also all necessary known_hosts were added in my .ssh directory. Everything worked fine from the command line, but Source Tree could not clone repos (stuck at checking source forever). For whatever reason the only way to acknowledge the RSA key in Source Tree was to download and use embedded Git (an authorization window finally popped up in the Source Tree UI). Everything has worked fine since.
I've been having trouble with this too. It just looked like the following (pathnames removed) and would spin endlessly.
But when I change it from SSH to HTTP in the dropdown in Stash it works:
I have reproduced this - when SSH is selected I have the problem above but when I select HTTP in that dropdown it works.
Unfortuantely it is a private repo in my company, using Beanstalk, it seems to happen with all repos. I think I just need to fully uninstall SourceTree and reinstall, but regardless of what tools I use there seems to be configuration files and stuff still left in the registry because it knows my settings from the last install when I start it up.
Can you tell me how to fully uninstall SourceTree without a trace so I can install it and try again?
I'm having the same problem - infinite "Checking source..." while trying to clone a repo. I can even click on the browse icon to the right, and it will find the hosted repo (after asking for username and password), and says it is able to connect. However, selecting these hosted repos from the browse screen just brings me back to the original screen with the infinite "Checking source..." and unclickable "Clone" button.
What "fixed" the issue for me on every dev's workstation that had issues was to uninstall every old version of git & git toolset &, reboot, then install git 1.83/1.84 and re-install SourceTree. So no real root cause that I ever pinned down, and I even lost the energy to troubleshoot it. In one instance I found a repo just wouldn't stop acting squirrely and I had to do a clone --bare, delete it from Stash, and then recreate it and do a push --mirror and then everyone was fine.
I'm experiencing the same issue.
The 'owner" select box keeps loading forever and ever
Screen Shot 2014-11-05 at 9.03.52 AM.png
I followed the advices here https://confluence.atlassian.com/pages/viewpage.action?pageId=270827678 as it seams to be something related to public and private keys, but it didn't help. I managed to go until the 5'th step but the file ~/.hgrc does not excist into my user directory. Any suggestion?
Looks like answer from @SysDev Licensing is the correct one. How to verify you are having the same issue:
(assuming that you can clone your git repo from command line and push to bitbucket)
cd "C:\Program Files (x86)\Atlassian\SourceTree\tools\putty" plink firstname.lastname@example.org
(credit goes to @SysDev Licensing)
What works for me is to first use Putty to manually attach to the server. Once the ssh key gets saved in the Registry, the endless "Checking Source" goes away and I get prompted for a password.
This is when using putty (obviously) and attaching to a private repository, not a service like BitBucket
I have the problem too. Pull, push and fetch never completes. It just spins and spins. It happens with all my repos on the specific PC. Other PCs doesn't do it with the same repos.
If I open up the terminal and perform the command there, things work great, so git seems to be just fine. Seems to be pointing to something in SourceTree getting corrupted. Last time I experienced this, I had to do a full reinstall to get it back to normal for a while (the local clones were kept, so It can't be something in the clones)
When is this going to be fixed? It's such a PITA to run plink.exe, especially with v2.4.8 and plink in in users home directory in `~/AppData/Local/SourceTree/app-2.4.8/tools/putty/` directory !!
Surely there must be a way for SourceTree to prompt the user to do something, or make the connection or store the keys.
Such a time waster and sooooo frustrating !!!
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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...
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!
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