"did you run git update-server-info" error on a Github repository

Question

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.git/info/refs not found: 
did you run git update-server-info on the server?

How can I fix this?

What operation were you performing that raised this error? Is it a brand new repo? And if so, did you follow the initial instructions for making a first checkin? — jdi, Feb 18 '12 at 17:12
@jdi: Obviously `git remote add something https://github.com/username/my_project.git` and then `git push something`. — Boris Stitnicky, Apr 10 '13 at 10:49
This is Git-speak for "Repository not found. You may have mistyped something." LOL — Luke Puplett, Apr 19 '13 at 10:29

score 77 · Answer 1 · answered Nov 06 '12 at 13:46

77

You might have changed your repository name

In your local repository edit the file:

.git/config

Then check:

[remote "origin"]
   url =

that the URL matches your remote repository

answered Nov 06 '12 at 13:46

Javier Giovannini

2,302
1
19
21

5

With newer versions of git you can do this from the command line: git remote set-url origin git@github.com:repoaccountname/repo-name.git – Arjun Mehta Apr 09 '14 at 23:14

navins · Answer 2 · 2013-03-15T06:43:49.923

44

Did you create a new repository on the http://github.com with the same name?

If not, do it! And make sure each letter is correct and case sensitive.

edited Mar 15 '13 at 06:43

answered Aug 27 '12 at 06:46

navins

3,429
2
28
29

score 27 · Answer 3 · answered Aug 28 '12 at 18:36

27

In my case my github account did not have permissions to the repo. Added the github account as a collaborator for the repo and that fixed it.

answered Aug 28 '12 at 18:36

amolk

1,387
13
13

score 14 · Answer 4 · answered Oct 23 '12 at 08:29

14

This error mostly caused by WRONG URL, please check:

http or https
URL Name
username@git_url
wrong git name

answered Oct 23 '12 at 08:29

Wendy William

305
2
4

score 9 · Answer 5 · answered Feb 18 '12 at 21:39

9

It looks like that's a private (or deleted) repository; if you visit the repository page while logged it'll give you the real URL, which'll probably be https://TeaCodie@github.com/TeaCodie/TeaCodie-Website.git , i.e. with a username specified?

answered Feb 18 '12 at 21:39

FauxFaux

2,445
16
20

1

USER ERROR...i think i have sorted it now...but thats for your help – Paul Feb 18 '12 at 22:09
16

Please explain what it was – Tyler Aug 21 '12 at 00:23
yes! this was the solution. i was pulling off a deleted repository. someone silently deleted the repo without informing me :P – Abbas Gadhia May 30 '13 at 12:03

score 7 · Answer 6 · answered Sep 26 '12 at 20:36

7

Also make sure the repo you've entered is cased correctly (it's case sensitive).

answered Sep 26 '12 at 20:36

alexvance

1,114
1
11
31

1

Thanks, this was my case. I've changed my username from "Enrichman" to "enrichman"! – Enrichman Nov 07 '12 at 13:42

score 6 · Answer 7 · answered Apr 07 '13 at 19:58

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

score 6 · Answer 8 · answered Aug 04 '13 at 11:27

6

My issue was that I used the clone https url widget provided by github. That URL doesn't work for private repositories as you need to add a username to the front of it.

Example: a private repo owned by john and named widget with collaborator sam the correct url would be:

https://sam@github.com/john/widget.git

The github provided url:

https://github.com/john/widget.git

The error message leaves much to be desired.

answered Aug 04 '13 at 11:27

John LaBarge

149
1
9

1

thank you. exactly my problem and this solution worked. – AdityaSaxena Jan 20 '14 at 01:49

score 5 · Answer 9 · answered Jun 02 '13 at 16:48

5

Make sure that your user account is added to the repository as a collaborator.

Setting --> Collaborators

answered Jun 02 '13 at 16:48

Mark

3,389
2
28
52

score 2 · Answer 10 · answered Feb 02 '13 at 17:56

This happened to me and at first it was not apparent what had gone wrong. The previous day I had renamed my repo on github.com only changing the first character of the repo name from a lowercase letter to uppercase. I was not aware that the repo name in the origin URL was case-sensitive unit I received the error which contained the text, "did you run git update-server-info on the server." Once I edited the .git/config file to correct the case of the same letter in the origin URL, the problem was solved, the error no longer occurred and I was once again able to push my changes up to the repo on github.com. Another bit of advice: if you make changes to your repo on github, make sure to test sync'ing your local repo right away. In my case, I did not and it was the next day when I had tried to sync and couldn't because of the error and I forgot that I had renamed the repo, so I was scratching my head for a bit. Had I tested sync'ing right away, I would have caught this problem right away.

score 2 · Answer 11 · edited Oct 25 '13 at 18:57

2

I met up with the same problem.
How I solved this problem is:
I use git bash to create a new repo, when I typed "git push origin master" It reported

"fatal: https://github.com/TeaCodie/TeaCodie-Website.git/info/refs not found: did you run git update-server-info on the server?"

Finally, I found there was not a repo on the github at all.
You'd better create a new repo first on github.

Maybe this experience can help somebody.

edited Oct 25 '13 at 18:57

Seth Tisue

29,985
11
82
149

answered Feb 24 '13 at 15:04

FrankFan

57
5

1

"did you run git update-server-info..." is a less useful question to ask than "did you misspell the repo". – Camille Goudeseune Feb 17 '15 at 20:22

score 1 · Answer 12 · answered Feb 06 '13 at 17:30

1

I received this same error when I attempted to git clone something from Kiln what was actually a Mercurial repository.

answered Feb 06 '13 at 17:30

John Rasch

62,489
19
106
139

Same here : was trying to clone an SVN repository by mistake. – sglessard Apr 30 '13 at 15:28

score 0 · Answer 13 · answered Sep 28 '12 at 17:42

0

In my case I was using the wrong protocol in the repository URL (http instead of https)

answered Sep 28 '12 at 17:42

Julien

1,158
9
19

score 0 · Answer 14 · answered Jan 20 '13 at 03:14

0

This error could also happen if the repository you are attempting to reach was deleted.

answered Jan 20 '13 at 03:14

wonton

7,568
9
56
93

score 0 · Answer 15 · answered Aug 02 '13 at 12:49

0

In my case I had old version of the git. Upgrade to latest version fixed this issue.

answered Aug 02 '13 at 12:49

Sergey Demchenko

2,924
1
24
26

score 0 · Answer 16 · answered Aug 28 '13 at 07:36

probably you were trying to clone like this:

git clone https://github.com/TeaCodie/TeaCodie-Website.git

Then you got this error:

fatal: https://github.com/TeaCodie/TeaCodie-Website.git/info/refs not found: did you run git update-server-info on the server?

Here is what worked for me:

git clone https://github.com/TeaCodie/TeaCodie-Website.git/.git

because the directory "info/refs" is in the .git directory.

Arjun Mehta · Answer 17 · 2014-04-09T23:12:21.827

0

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

edited Apr 09 '14 at 23:12

answered Apr 09 '14 at 20:34

Arjun Mehta

2,500
1
24
40

score 0 · Answer 18 · answered Aug 28 '15 at 10:08

I got this issue when using GitStack. I looked into C:/GitStack/apache/logs/error.log and found that GitStack was looking for the repository in the wrong location although its settings said D:/Repositories (my custom location), GitStack looked for the repositories in its default location. So I simply went and save the settings again from GitStack admin page. It solved the problem.

score 0 · Answer 19 · answered Apr 12 '16 at 20:42

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.

score 0 · Answer 20 · answered Jul 13 '19 at 23:02

I encountered this message when using Jenkins 2.176.1 and git plugin 3.10.0 using a very old command line git version (1.7.1) as included on CentOS 6.

The message does not occur on newer versions of command line git (1.8 or later) with the Jenkins git plugin.

Upgrading to a newer command line git version resolves the problem.

Officially, the Jenkins git plugin does not support command line git 1.7.1. The minimum supported version is command line git 1.7.10. Many Jenkins git plugin use cases require at least command line git 1.9.0.

Command line git 1.7.1 behaves differently than later versions when a repository has been initialized (with git init) and then a git fetch is performed with a refspec which references 'origin'. Later versions of command line git do not have the same problem.

"did you run git update-server-info" error on a Github repository

20 Answers20

Linked

Related