I\'m using the github Gui from their website to manage my repos, and I\'m getting the following error:
fatal: https://github.com/TeaCodie/TeaCodie-Website.gi
This error could also happen if the repository you are attempting to reach was deleted.
In my case, I was trying to clone a private repository in our group Github account to me laptop:
Yuqians-MacBook-Air:regenerateSNID yuqianliu$ git clone https://github.com/nyusngroup/velocity_CCSNe.git
Cloning into 'velocity_CCSNe'...
fatal: https://github.com/nyusngroup/velocity_CCSNe.git/info/refs?service=git-upload-pack not found: did you run git update-server-info on the server?
I found two ways can solve this.
(1) Use http instead of https. It asks me the name and password of our group Github account. After I entered the information, I can clone it.
Yuqians-MacBook-Air:regenerateSNID yuqianliu$ git clone http://github.com/nyusngroup/velocity_CCSNe.git
Cloning into 'velocity_CCSNe'...
Username for 'http://github.com':nyusngroup
Password for 'http://nyusngroup@github.com':
(2) Add my Github account to the collaborators of the private repository in our group Github account, as pointed by Monkey King's answer above.
I got the same problem while using a github repository, and connecting to it via https, while using the OS X Keychain Credential helper.
My problem was that I had the wrong credentials stored in OS X's Keychain (I was using the email address that I used to sign up for github.com rather than the [username]@github.com address it provides you). I deleted the old account in the keychain and only left the @github.com one and it fixed the problem.
Not sure if it is related, but when I checked the user.email
local config:
git config -l
it showed the incorrect email address as well, so I updated the local git user.email
to use the correct account too:
git config user.email <username>@github.com
In my repo's directory on my machine in the terminal I had to reset the origin url
:
git remote set-url origin git@github.com:repoaccountname/repo-name.git
This error mostly caused by WRONG URL, please check:
In my case I was using the wrong protocol in the repository URL (http instead of https)