Article version:

HTTPS cloning errors

There are a few common errors when using HTTPS with Git. These errors usually indicate you have an old version of Git, or you don't have access to the repository.

Here's an example of an HTTPS error you might receive:

> error: The requested URL returned error: 401 while accessing
> fatal: HTTP request failed
> Error: The requested URL returned error: 403 while accessing
> fatal: HTTP request failed
> Error: not found: did you run git
> update-server-info on the server?

Check your Git version

There's no minimum Git version necessary to interact with GitHub, but we've found version 1.7.10 to be a comfortable stable version that's available on many platforms. You can always download the latest version on the Git website.

Ensure the remote is correct

The repository you're trying to fetch must exist on GitHub, and the URL is case-sensitive.

You can find the URL of the local repository by opening the command line and typing git remote -v:

$ git remote -v
# View existing remotes
> origin (fetch)
> origin (push)

$ git remote set-url origin
# Change the 'origin' remote's URL

$ git remote -v
# Verify new remote URL
> origin (fetch)
> origin (push)

Alternatively, you can change the URL through ourGitHub Desktop application.

Provide an access token

If you have enabled two-factor authentication, or if you are accessing an organization that uses SAML single sign-on, you must provide a personal access token instead of entering your password for HTTPS Git.

Check your permissions

When prompted for a username and password, make sure you use an account that has access to the repository.

Tip: If you don't want to enter your username and password every time you interact with the remote repository, you can turn on password caching.

Use SSH instead

If you've previously set up SSH keys, you can use the SSH clone URL instead of HTTPS. For more information, see "Which remote URL should I use?"

Ask a human

Can't find what you're looking for?

Contact us