Coder Perfect

During git clone, “Unable to find remote helper for ‘https'”


I’m having trouble cloning HTTPS repositories. I can successfully clone SSH repositories, but not HTTPS repositories. Because I’m behind a corporate firewall, I can’t test the GIT protocol.

This is what I’m attempting to achieve:

$ git clone
Cloning into gitflow...
fatal: Unable to find remote helper for 'https'

So far, I’ve tried the following: (based on Google searches)

I’ve tried everything I can think of on the internet but haven’t had any results. Is there anyone who can assist me?

Version of Git

Ubuntu 11.04 is the operating system.

Asked by Ben K

Solution #1

This appears to be caused by not having (lib)curl-devel installed while compiling git.

If you install (lib)curl-devel, and then rebuild/install git, this should solve the problem:

$ yum install curl-devel
$ # cd to wherever the source for git is
$ cd /usr/local/src/git-1.7.9  
$ ./configure
$ make
$ make install

On Centos 6.3, this worked for me.

If you don’t have yum, you can get curl-source devel’s code here:

If you’re using Ubuntu instead, follow these steps:

sudo apt-get install libcurl4-openssl-dev 

Answered by TastyCode

Solution #2

You could utilize the git transport if you’re trying to clone.

git clone git:/, for example.

Vaio ~/Myworks/Hero $ git clone git://

Initialized empty Git repository in /home/nthillaiarasu/Myworks/Hero/fog/.git/
remote: Counting objects: 41138, done.
remote: Compressing objects: 100% (13176/13176), done.
remote: Total 41138 (delta 27218), reused 40493 (delta 26708)
Receiving objects: 100% (41138/41138), 5.22 MiB | 58 KiB/s, done.
Resolving deltas: 100% (27218/27218), done

Answered by Thillai Narayanan

Solution #3

OPKG as package manager on a QNAP system or any other system:

Along with git, you’ll need to install git-http. For example:

opkg install git-http

Answered by CWBudde

Solution #4

I addressed the problem by using “git:/” instead of “https://.” The last command I gave was:

git clone --recursive git://

Answered by cecheverria

Solution #5

When we checked in our situation, the issue had been resolved.

git --exec-path

was pointing to a way that had vanished. (It was pointing to the place where we compiled git, not where we copied it afterwards for others to see.)

We did a:

export GIT_EXEC_PATH=<path_of_/libexec/git-core/>

and solved.

Answered by Pedro Reis

Post is based on