1
0
mirror of synced 2025-12-25 02:17:36 -05:00
Files
docs/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md
Arthur Casals 92e8c51742 Update content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md
Added suggested changes

Co-authored-by: Felicity Chapman <felicitymay@github.com>
2020-10-21 20:19:41 +02:00

3.5 KiB

title, intro, redirect_from, versions
title intro redirect_from versions
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.
/articles/error-the-requested-url-returned-error-403/
/articles/error-the-requested-url-returned-error-401/
/articles/error-did-you-run-git-update-server-info-on-the-server/
/articles/error-the-requested-url-returned-error-403-while-accessing-https-github-com-user-repo-git-info-refs/
/articles/https-cloning-errors
free-pro-team enterprise-server
* *

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

> error: The requested URL returned error: 401 while accessing
> https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git/info/refs?service=git-receive-pack
> fatal: HTTP request failed
> Error: The requested URL returned error: 403 while accessing
> https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git/info/refs
> fatal: HTTP request failed
> Error: https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git/info/refs 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 {% data variables.product.product_name %}, 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 {% data variables.product.product_location %}, 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  https://github.com/github/reactivecocoa.git (fetch)
> origin  https://github.com/github/reactivecocoa.git (push)

$ git remote set-url origin https://github.com/github/ReactiveCocoa.git
# Change the 'origin' remote's URL

$ git remote -v
# Verify new remote URL
> origin  https://github.com/github/ReactiveCocoa.git (fetch)
> origin  https://github.com/github/ReactiveCocoa.git (push)

Alternatively, you can change the URL through our {% data variables.product.prodname_desktop %} application.

Provide an access token

To access {% data variables.product.prodname_dotcom %}, you must authenticate with a personal access token instead of your password. For more information, see "Creating a personal access token."

{% data reusables.command_line.provide-an-access-token %}

Check your permissions

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

{% tip %}

Tip: If you don't want to enter your credentials every time you interact with the remote repository, you can turn on credential caching. If you are already using credential caching, please make sure that your computer has the correct credentials cached. Incorrect or out of date credentials will cause authentication to fail.

{% endtip %}

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?"