Git: Unable to find remote helper for 'ssh'

Question

Whenever I try to push to a remote repository via SSH I keep getting the following error message: fatal: Unable to find remote helper for 'ssh'.

Using:

The thing is that I had the exactly same approach working quite a while ago on one of the projects and now decided to try using it for another.

OpenSSL, Git and Curl are all in place.

Any suggestions?

Welcome to SO! more information on what exact command were you using and also details about if this repo that you are trying to push is yours or you cloned from someone in github might help us diagnose the issue.. — uday, Apr 11 '16 at 15:37
OpenSSL is not OpenSSH. You need to have something that handles ssh. Are you using something like SourceTree? It's installer adds all needed dependencies. — Mir, Apr 11 '16 at 15:50
@Mir I've got OpenSSH along with Cygwin, as I said previously - no changes were made and the same setup was working before. I've tested SSH bridge with the server and it works perfectly fine. — Vytautas Grigaravicius, Apr 11 '16 at 15:51
@uDaY No, everything's set up in test environment. I have created a blank bare repo on the server and trying to push the master branch of a project on local machine to it. Just tried runing git remote show against the remote repo and that one produced the same error, however when added -n option it worked. Any ideas? — Vytautas Grigaravicius, Apr 11 '16 at 15:55
@KeithThompson Yes and it all works, I can ssh to the server using RSA token. It looks to me like there's an issue with git rather than SSH itself. — Vytautas Grigaravicius, Apr 11 '16 at 16:09

score 2 · Accepted Answer · answered Jul 19 '17 at 14:30

2

I had the same error message. I guess I had a malformed ssh url in the git command.

I removed ssh part ssh:://, changed host name (taken from ~/.ssh/config) to IP address, and that worked.

answered Jul 19 '17 at 14:30

I agree about the malformed ssh url... try 'ssh://' instead of 'ssh:://' (note the double-colon) – Scotty Nov 09 '18 at 19:30

score 1 · Answer 2 · edited May 23 '17 at 12:23

1

Decided to give this approach another try and it worked. Seemed to be some sort of an issue with curl.

Thanks anyway!

edited May 23 '17 at 12:23

Community

answered Apr 11 '16 at 16:16

2 Answers2