If you see this error when cloning a repository, it means that the repository does not exist or you do not have permission to access it. There are a few solutions to this error, depending on the cause.
Typos happen, and repository names are case-sensitive. If you try to clone
email@example.com:user/repo.git, but the repository is really named
User/Repo you will receive this error.
To avoid this error, when cloning, always copy and paste the clone URL from the repository's page. For more information, see "Cloning a repository."
To update the remote on an existing repository, see "Changing a remote's URL".
If you are trying to clone a private repository but do not have permission to view the repository, you will receive this error.
Make sure that you have access to the repository in one of these ways:
- The owner of the repository
- A collaborator on the repository
- A member of a team that has access to the repository (if the repository belongs to an organization)
In rare circumstances, you may not have the proper SSH access to a repository.
You should ensure that the SSH key you are using is attached to your GitHub user account. You can check this by typing the following into the command line:
ssh -T firstname.lastname@example.org # Hi username! You've successfully authenticated, but GitHub does not # provide shell access.
For more information, see Generating SSH Keys.
If all else fails, make sure that the repository really exists on GitHub! If you're trying to push to a repository that doesn't exist, you'll get this error.