Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Servers, nginx and Docker

git clone fails: Unable to find remote helper for 'https'

Errorfatal: Unable to find remote helper for 'https'

Short answer

Git handles https through a helper program named git-remote-https, which is built with curl support. If git was compiled without the curl development files, that helper is missing. A mistyped scheme in the URL gives the same message. Fix the URL, or install curl headers and rebuild git.

  • Applies to Git 2.4x, Ubuntu 24.04
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Look at the URL scheme you typed, then list the remote helpers next to git's core programs. If git-remote-https is not in the list, the helper is missing.

    git remote -v
    ls "$(git --exec-path)" | grep remote
  2. 2Match what you see, then jump to its fix

    1. 1git came from a tarball or a custom build, and the grep shows no git-remote-httpsgit was built from source without curl supportFix
    2. 2The message names a scheme other than https, or the URL has a stray space or letterThe URL scheme is mistypedFix

What does the error look like?

  • fatal: Unable to find remote helper for 'https'

Cause 1 of 2

git was built from source without curl support

1Check

Git ships a curl family of helpers, including git-remote-http and git-remote-https, to handle http transports. Building from source needs curl among its required libraries.

git --version
which -a git

2Fix

Install the build dependencies from the Git book, rebuild and reinstall git. On Debian or Ubuntu that list includes libcurl4-gnutls-dev.

sudo apt-get install dh-autoreconf libcurl4-gnutls-dev libexpat1-dev gettext libz-dev libssl-dev
make configure
./configure --prefix=/usr
make all
sudo make install

3Verify

git-remote-https is now listed, and a clone works.

ls "$(git --exec-path)" | grep remote
git clone https://github.com/git/git.git

Confirmed by git-scm.com

Did this fix it?

Cause 2 of 2

The URL scheme is mistyped

1Check

When a URL uses a transport Git cannot handle itself, Git invokes git remote-<transport> for it. A scheme such as htps or http s has no helper, so the lookup fails.

git remote -v

2Fix

Correct the URL and clone again.

git remote set-url origin https://example.com/team/repo.git
git clone https://example.com/team/repo.git

3Verify

The clone starts transferring.

git ls-remote https://example.com/team/repo.git

Confirmed by git-scm.com

Did this fix it?

How do I stop it coming back?

  • Install git from your distribution's package manager unless you need a newer version.
  • When you build git, keep the dependency list of the Git book in your build script.
  • Copy clone URLs from the hosting site rather than typing them.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Related fixes

Servers

dnf cannot install MySQL on Amazon Linux 2023

dnf cannot find a mysql-server package on Amazon Linux 2023

Amazon Linux 2023 documents MariaDB, not MySQL, as its database server, with packages named mariadb105 and mariadb105-server.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.