Cloning over SSH Doesn't Work for a Remote Account When Repo Has a Submodule

Ian Smithers August 29, 2018

I hope that subject line isn't confusing. :)

I am using Sourcetree and am pretty familiar with Git having used it via Bash for several years now. In Sourcetree if I take the repository URL that is hosted in Bitbucket which looks like:

git@bitbucket.org:team/repository.git

Then select Clone, add in the URL, choose Advanced Options and select Recurse Submodules - this will clone successfully.

If instead I add a Remote Account (which Sourcetree tells me makes cloning even easier (!)), search for my repository and then select Clone, it will clone the supermodule, but fail on the submodule with the error "fatal: error in sideband demultiplexer"

Which I have no idea what it means.

My Sourcetree settings are:

SSH Key is loaded via SSH Client PuTTY/Plink. This loads automatically and I enter my passkey and I can see it in the taskbar process. My public key is added to Bitbucket. I am on Sourcetree version 2.6.10.0 and Authenticaion is set to:

  • Hosting Service - Bitbucket
  • Protocol: SSH
  • Auth: OAuth
  • Username: iansmithers
  • With Authentication: OK showing and a green tick.

I've spent a few hours trying to figure out what this may be, and have cloned several submodule enabled repositories to see if it is isolated, but it isn't. It happens on them all - only when selecting 'Clone' from the Remote repositories screen. If I manually paste the clone URL in it works fine. Very confused.

2 answers

1 accepted

8 votes
Answer accepted
Pravin
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 4, 2018

Hi Ian, 

As discussed through the Support Ticket.

After several testing, I'm suspecting that error "error in sideband demultiplexerappears related to Putty SSH Agent. Git Bash uses Open SSH by default and Source Tree uses Putty SSH Client by default. 

Since it works on Git Bash which uses Open SSH, changing Source Tree to use Open SSH for its SSH Client works as you have tested. I would suggest to changing it to use OpenSSH as the SSH Client moving forward. 

To change SSH Client on Source Tree, navigate to : Tools > Options > General >> SSH Client Configuration >> SSH Client > Select OpenSSH. 

Thanks.
Pravin

Ian Smithers September 5, 2018

Thanks Pravin, pleasure dealing with you btw and much appreciated the assistance. :)

Like Pravin likes this
Femi Ojemuyiwa June 26, 2019

There is no Tools > Options > General on source tree for mac version 3.2.1

Been searching on how to resolve and hope someone somewhere has an answer as to why cmd line clone works and sourcetree doesn't 

Femi Ojemuyiwa June 27, 2019

So for anyone out there, I found the user account SSH key and not local machine key resolved my issue. as using command line git works fine with local machine, but source tree account being used wouldn't clone unless configured properly.

0 votes
Andrew Britton October 9, 2019

I was having a similar problem with cloning failing. Capturing network traffic showed that the Bitbucket server was simply dropping the SSH connection. 

Upgrading the embedded version of Plink to 0.73 fixed the issue for me.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events