[Solved-5 Solutions] Github: error cloning my private repository
Error Description:
Github: error cloning my private repository
Solution 1:
- Should we be able to clone private repositories with:
git clone orgname/reponame
click below button to copy the code. By Git tutorial team
- Because when we try that atm we getting the following error:
Cloning into 'reponame'...
fatal: remote error:
Repository not found.
click below button to copy the code. By Git tutorial team
- We can successfully use features like git pull-request
- These are the versions we use (hub is installed via brew):
$ git version [ruby-1.9.3-p194]
> git version 1.7.9
> hub version 1.10.1
click below button to copy the code. By Git tutorial team
Solution 2:
- Check spelling
- Typos happen, and repository names are case-sensitive. If we try to clone
git@github.com:user/repo.git,but the repository is really namedUser/Repowe will receive this error. - To avoid this error, when cloning, always copy and paste the clone URL from the repository's page. To update the remote on an existing repository, see "Changing a remote's URL .
Check permissions
- If we are trying to clone a private repository but do not have permission to view the repository, we will receive this error.
- Make sure that we 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)
- Check your SSH access
- In rare circumstances, we may not have the proper SSH access to a repository.
- we should ensure that the SSH key we are using is attached to your GitHub user account. we can check this by typing the following into the command line:
ssh -T git@github.com
Hi username! we've successfully authenticated, but GitHub does not
provide shell access.
click below button to copy the code. By Git tutorial team
- Check that the repository really exists
- If all else fails, make sure that the repository really exists on GitHub! If we're trying to push to a repository that doesn't exist, we'll get this error.
Solution 3:
- we have seen this on Windows, with msysgit 1.7.2.3. we have to fix the path to bin/curl-ca-bundle.crt. we had to specify the absolute path, using back-slashes:
git config --system http.sslcainfo "C:\Program Files (x86)\git\bin\curl-ca-bundle.crt"
click below button to copy the code. By Git tutorial team
- Or - not really recommended -we may choose to switch off SSL checks completely by executing:
git config --system http.sslverify false
click below button to copy the code. By Git tutorial team
- For both cases, this will result in changes to [git-install-dir]/etc/gitconfig file, which may be edited directly, too.
Solution 4:
- We run the cmd to view ca-certificates:
$ curl-config --ca
**/etc/ssl/certs/ca-certificates.crt**
click below button to copy the code. By Git tutorial team
- But actually we found the certificates at the path:
**/etc/ca-certificates/extracted/ca-bundle.trust.crt**
click below button to copy the code. By Git tutorial team
- Then add the config into ~/.gitconfig (if not existing, create it):
**vim ~/.gitconfig**
[http]
sslVerify = true
sslCAinfo = /etc/ca-certificates/extracted/ca-bundle.trust.crt
[user]
email = <email of github account>
name = <username of github account>
click below button to copy the code. By Git tutorial team
- It works!
.rbenv]$ git pull
remote: Counting objects: 70, done.
remote: Compressing objects: 100% (47/47), done.
remote: Total 70 (delta 39), reused 12 (delta 12), pack-reused 6
Unpacking objects: 100% (70/70), done.
From https://github.com/sstephenson/rbenv
c43928a..efb187f master -> origin/master
+ 37ec781...7e57b52 user-gems -> origin/user-gems (forced update)
Updating c43928a..efb187f
Fast-forward
libexec/rbenv-init | 4 ++--
libexec/rbenv-version-file | 1 +
test/init.bats | 2 +-
test/test_helper.bash | 25 +++++++++++++++----------
4 files changed, 19 insertions(+), 13 deletions(-)
click below button to copy the code. By Git tutorial team
Solution 5:
- We solved the problem installing the Git from: Locate the cert file path:
D:\Program Files\Git\mingw64\ssl\certs\ca-bundle.crt
click below button to copy the code. By Git tutorial team
- Configure the Git path:
git config --system http.sslcainfo "D:\Program Files\Git\mingw64\ssl\certs\ca-bundle.crt"
click below button to copy the code. By Git tutorial team
Learn git - git tutorial - gitbit errors cloning - git examples - git programs