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; } } }

SourceTree: plink unkown option "-p"

nickhhg

I'm receiving the below error when attempting to do anything with Git over SSH on a non-standard port, and was wondering if anyone could help solve the issue.

git -c diff.mnemonicprefix=false -c core.quotepath=false fetch --prune origin
plink: unknown option "-p"
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Completed with errors, see above.

Environment

Windows 10 Pro 64 bit

Sourcetree 2.5.4 (Windows)

Git 2.16.1 (System)

Git 2.15.1 (Embedded)

plink 0.70.2 (Embedded)

Putty/plink 0.70.0 (System)

TortoiseGit 2.6.0

Other Details

I believe the correct option to specify a port should be a capital "-P", but I don't understand why SourceTree is using a lowercase one.
Git URL format: ssh://user@domain.com:553/path/my-repo
Access to the Git repo via SSH is confirmed working with TortoiseGit on the same system

Accepted answers

All comments

minnsey

Hi

As far as I can see the only time we make use of the -P option is if there is an interaction with the remote that triggers a response indicating the server's host key is not cached or has changed.

We then re-run plink.exe with the -P option if required, but that should be uppercase.

If this is the case you should have been prompted by Sourcetree to accept the new SSH key, did this happen?

You can find out a bit more about what might be happening be enabling DEBUG logging, by changing ERROR to DEBUG in %localappdata%/Sourcetree/app-2.5.4/log4net.config

This will log to %localappdata%/Atlassian/Sourcetree/sourcetree.log you should be able to find any plink.exe calls with associated arguments in there.

nickhhg

I don't recall Sourcetree initially asking to accept the SSH key, but maybe that has something to do with possibly accepting it via TortoiseGit previously?.

I did attempt to completely remove Sourcetree and re-install it to try again. It did not prompt for accepting the SSH Key. If you can provide an idea of where/how to clear out cached keys I can attempt to do that.

On a recent attempt I accidentally misspelled the repo name in the URL (but everything else was correct), Sourcetree did prompt to accept the SSH key. This ultimately failed though because my repo name was incorrect. After correcting the spelling, it functioned as previously with the same output.

I made the log4net config change and did see a lot more output into sourcetree.log, but nothing that stood out or seemed to provide anymore info in relation to the error.

The command that Sourcetree is saying it's attempting to run (above), I attempted to run that manually in both Git Bash and PowerShell and got the exact same error in response

nickhhg

Just updated (System) Git to 2.16.2 (from 2.16.1) and it seems to have fixed the issue for Git when used from PowerShell or Git Bash, but issue remains with Sourcetree regardless of using System or Embedded Git.

Workaround found:

I have just managed to find a workaround for the issue by replacing SourceTree/app-*/tools/plink.exe with TortoiseGitPlink.exe (renamed to plink.exe). It should be noted that I tried to do the same by using Putty's plink.exe, but this did not work and resulted in the same issue.

This also explains the above where re-installing Git fixed the issue for Git via shell, because Git via shell looks at the GIT_SSH environment variable, which pointed to TortoiseGItPlink.exe when it was detected during re-installation of Git, meaning Git was using TortoiseGitPlink.exe and working.

SourceTree obviously does not use GIT_SSH environment variables, and prefers it's own plink.exe which for whatever reason I am having an issue with.

minnsey

Thanks for the detailed response. We will add it to our backlog to investigate.

Praneeth Muskula

I fixed this by going to Options=>General under the SSHClient configuration section, there is a dropdown for SSHClient.

I chose OpenSSH instead of "Putty / Plink". You may have to install openssh on your machine before you see this option in your dropdown. That fixed it for me.

minnsey

OpenSSH is picked up from the Git client, it should always be available.

Welcome!

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

Quick Links

Find more posts tagged with

sourcetree

windows