nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problem cloning a Gitlab when ssh destination is modified on Windows

Skullhanbons11

I currently use the Windows SSH agent, which holds several private keys that all work perfectly when accessed via the CLI. The issue arises when I try to clone repositories using a specific corporate GitLab key; the destination path has been modified—using gitlab@gitlab.example instead of the standard git@gitlab—and I believe this prevents SourceTree from recognizing both the SSH agent and the repository URL I want to clone.
In SourceTree, I have selected the "OpenSSH" option with the "automatically start SSH agent" setting disabled, as I already have the Windows SSH agent running at all times. Currently, the only way it works is if I manually add the SSH key and authenticate every single time I open the application.
Is there really no other way to automate the authentication? Or is there a way to ensure SourceTree uses the Windows SSH agent instead of its own?

I have attached the error message below:

Command: git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks ls-remote gitlab@gitlab.example.com:example/of/error/bla/bla-bla.git
Output:
Error: gitlab@gitlab.example.com: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

For any other doubts about this problem becasue a lack of context don't doubt to reply me as many times as needed.

If any further context is needed, please feel free to reply to this thread—don't hesitate to ask as many follow-up questions as necessary.

Thank you very much in advance.

Accepted answers

All comments

Tomislav Tobijas

@Skullhanbons11 cheers for the detailed explanation! One question — are you using the embedded or system git version?

I've managed to find something like this:

Use System Git: Go to Tools > Options > Git. Under Git Version, click Use System Git. This ensures Sourcetree uses the same Git executable and SSH environment as your CLI.

The issue could be caused by a conflict with Windows SSH agent you already have running.

Force Sourcetree to use native OpenSSH

Update SSH Client: Go to Tools > Options > General. Under SSH Client Configuration, ensure the SSH Client is set to OpenSSH
Use System Git: Go to Tools > Options > Git. Under Git Version, click Use System Git. This ensures Sourcetree uses the same Git executable and SSH environment as your CLI
Check Environment Variables: Ensure there is no GIT_SSH environment variable pointing to plink.exe or pageant.exe, as this will override your OpenSSH settings

You could also confirm if the Windows agent is correctly offering your keys to GitLab (which I suspect it does) by running ssh -T gitlab@gitlab.example.com

Cheers,
Tobi

Skullhanbons11

Thank you very much for the quick response!
Yes, I am currently using the system Git, as I had read that this might be the cause, but the issue persists nonetheless. I have also checked the environment variables, and they point to the Windows agent; unfortunately, the problem remains.

Arkadiusz Wroblewski

Hi Skullhanbons11

Building on Tobi's answer, it may be SourceTree may be using a different SSH client than your Windows SSH agent.

Which SourceTree version are you running? And does the exact git ls-remote command from your error work in PowerShell?

Atlassian fixed a related issue in SourceTree 3.4.32: SRCTREEWIN-14703.

check your version and try: git config --global core.sshCommand "C:/Windows/System32/OpenSSH/ssh.exe"

However, SourceTree ignoring this setting is tracked in SRCTREEWIN-10774 (Reviewing).

Best,

Arek🤠🧙‍♂️

Skullhanbons11

Thanks for the help guys!
I currently have the latest version, and I had already tried the command you suggested—having read the forum—but it seems it still points to its own agent. In any case, I saw a comment suggesting the creation of a "wrapper"; I attempted this by setting up an SSH configuration file, specifying the host and setting the user to "gitlab," but it didn't work.

Tomislav Tobijas

Hmmm 🤔

I mean, you could try running

ssh -G gitlab.example.com

To show which SSH configuration is actually being applied. You could also try ssh -vvv -T gitlab@gitlab.example.com to see which keys are being offered. 👀

But I really haven't worked that much with SSH keys so I'm maybe not the best person to troubleshoot it.

What I'd maybe suggest is trying to check Developer community → folks there use these things much more and probably will be able to help out 🤞

Tinker Fadoua - [Seibert US]

Welcome to the Atlassian Community @Skullhanbons11 !

I didn't want to copy/paste suggestions from the gitlab forum where they do have lot of recommendations.

Some of them are little bit old but very helpful.

Best,

Fadoua

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

sourcetree

git

ssh

gitlab

openssh