fatal: The remote end hung up unexpectedly with a fetch upstream

Question

I am following the instructions on github for forking a repo but everything up to not including configure the remotes works. I am told to run the following code but git fetch upstream returns the following fatal: The remote end hung up unexpectedly Whats causing this, and could someone explain what it means to configure the remotes.

$ cd Spoon-KnifeChanges the active directory in the prompt to the newly cloned "Spoon-Knife" directory
$ git remote add upstream git://github.com/octocat/Spoon-Knife.gitAssigns the original repo to a remote called "upstream"
$ git fetch upstream

score 3 · Accepted Answer · edited May 23 '17 at 12:12

3

Why not just start fresh:

$ rm -rf Spoon-Knife
$ git clone git://github.com/octocat/Spoon-Knife.git
$ cd Spoon-Knife
$ git remote add upstream git://github.com/octocat/Spoon-Knife.git
$ git fetch upstream

As for the remote end hung up unexpectedly error, see this Stack Overflow question (among many) -- most likely reason is that your SSH keys weren't set up correctly.

edited May 23 '17 at 12:12

Community

1
1

answered Mar 06 '12 at 20:42

Marvin Pinto

30,138
7
37
54

I am not getting a fatal: The remote end hung up unexpectedly error for cloning. huh? – Cool Guy Yo Mar 06 '12 at 20:46
well I have run ssh -T git@github.com and it authenticates fine. – Cool Guy Yo Mar 06 '12 at 20:58
I followed them all and as soon as I run git clone I get a fatal: The Remote end hung up. – Cool Guy Yo Mar 06 '12 at 21:03
I am running mac osx and I am running them exactly no sudo or nothing. – Cool Guy Yo Mar 06 '12 at 21:22
2

omg so sorry, I was typing the wrong username i.e. anders instead of anderskitson – Cool Guy Yo Mar 06 '12 at 21:27

fatal: The remote end hung up unexpectedly with a fetch upstream

1 Answers1