github - Git, fatal: The remote end hung up unexpectedly - Stack Overflow
to customize your list.
Join the Stack Overflow Community
Stack Overflow is a community of 6.6 million programmers, just like you, helping each other.
J it only takes a minute:
When I tried to run
git push origin master --force
I just got
Counting objects: 2649, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (), done.
error: RPC result=22, HTTP code = 413 | 116 KiB/s
fatal: The remote end hung up unexpectedly
Writing objects: 100% (), 449.61 MiB | 4.19 MiB/s, done.
Total 2504 (delta 1309), reused 2242 (delta 1216)
fatal: The remote end hung up unexpectedly
Everything up-to-date
Is it something to do with not being secure? I tried creating a public key as in the answer for
and running it again, but it still doesn't work. Am I not actually using the key? If so, how do I use it?
This looks similar to .
Probably it's worth trying to switch from http protocol to ssh:
$ git remote add origin :username/project.git
The problem is due to git/https buffer settings.
In order to solve it (taken from )
git config http.postBuffer
And run the command again
Cause : The default file post size for Git has been exceeded.
Solution :
Navigate to repo.
Run the following command to increase the buffer to 500MB after navigating to the repository:
git config http.postBuffer
You might get an error like this
error: could not lock config file .git/config: No such file or
that is because you dont have a local .git/config file You can get it working by this command
git config --global http.postBuffer
Just to add this (because this was the first entry when I googled):
This error can also be thrown by missing writing access for the repository.
In my case I created the repo with the root account of my server and actually forgot about that later so the git user couldn't write the pushes into the directory.
Other solutions didn't work in my case, doing a garbage collection fixed it for me:
git gc --aggressive
In our case, the problem was a clone that wrote a .git/config file which contained a url entry that was a read only access method.
Changing the url from the :// method to the @ method fixed the problem.
Running git remote -v illuminated the issue some.
66.4k156496
You probably did clone the repository within an existing one, to solve the problem can simply clone of the repository in another directory and replicate the changes to this new directory and then run the push.
Another addition, since I encountered this error a different way and Google took me here.
My problem wa one camelCase and one not. Apparently, GIT stops you doing this without telling you why. So if your branches are different from the remote only in the capitalization, try changing them to be identical.
I happened to have the same error at pull.
I have done the "http.postBuffer" trick. It solved it, but when I wanted to push, I encountered the error again.
What solved my problem:
1. Cloned it to an other folder with an other virtual machine. (Linux).
2. I've done my changes.
3. Pushed it with the original virtual machine where I initially couldn't push. (Windows)
I got this error when I had incorrect keypair in .ssh. Adding the pubkey to github (in settings) fixed this issue for me.
1,66511014
If you are using git for windows (and you likely are, if you are doing this on a windows machine), and none of the other fixes here worked for you, try going to , and getting a version on or after version 2.4.5.
Fixed it right up for me.
I was able to get around this issue using Git Shell.
Each repository
gives you HTTPS/SSH/Subversion URL's that you can use to download using Shell, see here: .
Based on GitHub's recent changes, SSH seems to be the best method.
Command to use in Shell:
git clone "URL of repo goes here w/ no quotes"
5,396113553
I have the same problem. I noticed from the git web page that the SSH clone URL have the next structure:
:user/project.git
I could resolve my problem just changing the ":" by "/", as follows:
/user/project.git
may be this can be helpful.
I got this error when I had misspelt my remote branch name
Contrary to one of the other answers - I had the problem on push using ssh - I switched to https and it was fixed.
git remote remove origin
git remote add origin https://github..com/user/repo
git push --set-upstream origin master
Seems almost pointless to add an answer, but I was fighting this for ages when I finally discovered it was Visual Studio Online that was suffering a sporadic outage. That became apparent when VS kept prompting for creds and the VSO website sometimes gave a 500.
Counting objects: 138816, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (), done.
error: unable to rewind rpc post data - try increasing http.postBuffer
error: RPC curl 56 SSL read: error::lib(0):func(0):reason(0), errno 10054
The remote end hung up unexpectedly/138816), 33.30 MiB | 3.00 KiB/s
Writing objects: 100% (816), 50.21 MiB | 3.00 KiB/s, done.
Total 138816 (delta 100197), reused 134574 (delta 96515)
fatal: The remote end hung up unexpectedly
Everything up-to-date
I set my HTTP post buffer back to 2Mb afterwards, since I actually think it works better with many smaller posts.
13k1091129
This may occur after updating your OSX platform.
Open Terminal and navigate to your .ssh-folder, and enter ssh-add -K ~/.ssh/id_rsa
protected by ♦
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10
on this site (the ).
Would you like to answer one of these
Not the answer you're looking for?
Browse other questions tagged
The week's top questions and answers
Important community announcements
Questions that need answers
By subscribing, you agree to the
rev .24680
Stack Overflow works best with JavaScript enabled