Git, fatal: The remote end hung up unexpectedly

please show output of `git remote -v` – CharlesB Mar 06 '13 at 06:59

possible duplicate of [Git fails when pushing commit to github](http://stackoverflow.com/questions/2702731/git-fails-when-pushing-commit-to-github) – CharlesB Mar 06 '13 at 07:01

git config http.postBuffer 524288000 # it works for me – Hari Das Oct 25 '14 at 14:37

if you get `error: could not lock config file .git/config: No such file or directory` see http://stackoverflow.com/a/32329453/827525 – niksmac Sep 16 '15 at 04:03

I could not get any of the suggested solutions to work. Then I tried GitKraken. It is one of the few Git programs that doesn't use git.exe. GitKraken could do it. After GitKraken had pushed the repository I could switch back to git.exe and sync without any issues. – lars pehrsson Feb 26 '17 at 10:53

it might be due to network issues – AmiNadimi Jun 06 '17 at 07:21

@larspehrsson Please add this as an answers. This solved the problem for me using GitKraken instead, apparently the "official" git package is broken on windows. – aggaton Aug 07 '21 at 18:41

I need the buffer to be higher than 500MB - is that possible? It doesn't seem to make a difference if I make the postBuffer number any higher... – jowie Sep 11 '13 at 13:45

Thanks for the link - I sorted the issue by splitting the push into smaller chunks. If I have a problem again I know where to look! – jowie Sep 30 '13 at 08:13

This solves my issue as well, I'm guessing it's because a couple of my files went over the default allowed maximum transfer size supported by git? – ffledgling Apr 04 '14 at 08:18

As I understand it , git commits as a transaction. sum of all your files were bigger then the http post limit – Roman M Apr 04 '14 at 20:24

doesn't solve it for me: git -c diff.mnemonicprefix=false -c core.quotepath=false push -v --tags origin develop:develop Pushing to git@github.com:foo/baa.git ERROR: Repository not found. fatal: The remote end hung up unexpectedly Completed with errors, see above – SuperUberDuper Jan 21 '15 at 12:11

@SuperUberDuper it looks like you have a different issues. Your ERROR is Repository not found – Roman M Jan 21 '15 at 14:48

Would it be a good idea to use this with `--global`? I deal with large repositories regularly. – DaAwesomeP Feb 02 '15 at 20:55

I had a similar problem on Windows 7. After hours of googling, comming accross this post and doubling the buffer size, I discovered it was my antivirus software that was causing the issue – user28864 Feb 15 '17 at 23:36

This helps in some cases where the remote end hangs up, but I think in those cases you can see that it fails before all of the objects have been transferred. – mc0e Mar 14 '17 at 05:47

issue isn't publicly available anymore :( – shivam13juna Feb 14 '19 at 10:53

@shivam13juna nothing is ever deleted from the internet: :) https://web.archive.org/web/20170119225336/http://github.com/gitlabhq/gitlabhq/issues/3099 – Roman M Feb 17 '19 at 09:06

I ran "git config http.postBuffer 524288000", but still issue not resolved, it still saying the same, the remote end hung up unexpectedly – Narendra Feb 25 '20 at 01:38

@jowie I have written an [answer](https://stackoverflow.com/a/64565533/) attempting to note why this value can be as high as 2000000000 (2 GB), and what else needs to be done to make it work. – Asclepius Oct 28 '20 at 02:16

You can also use `git config ssh.postBuffer 524288000` if posting over ssh instead of http. – John M May 11 '15 at 21:01

For some cases `git config --global http.postBuffer 100000000` – Job M Nov 11 '19 at 13:23

I get 'fatal: not in a git directory' after execution of this command – ka3ak Feb 05 '20 at 13:44

@JohnM This option doesn't seem to exist, it's not documented in the man page or https://git-scm.com/docs/git-config – Nobody Feb 10 '20 at 11:58

I have written an [answer](https://stackoverflow.com/a/64565533/) attempting to note why the `http.postBuffer` value can possibly be as high as 2000000000 (2 GB), and what else needs to be done to make the push succeed. – Asclepius Oct 28 '20 at 02:29

Why can't I just switch from http to https? – DanielLC Mar 07 '13 at 02:58

bash-3.2$ git remote add origin git@github.com:xxx/xx.git fatal: remote origin already exists. WHY ? – almaruf Nov 03 '14 at 10:36

@almaruf it is because the remote `origin` is already there and you are trying to replace it. git doesn't allow that. So you have to first do `git remote rm origin` then try again. It would work – Alfie Apr 25 '15 at 11:28

make sure you initialise the project if it's a new fresh clone with `git init` – Raul Jul 21 '16 at 09:29

you can use either the git protocol over ssh (which requires ssh keys) or the https protocol which requires username and password through a personal access token – I prefer the later – Raul Jul 21 '16 at 09:30

The good point of SSH comparing HTTPS is that you can use one ssh key for several repositories and git hostings. I use one key for github, bitbucket and gitlab in despite of different usernames for every hosting. It saves a lot of time for fetch & push operations. – Vitalliuss Sep 19 '16 at 15:51

Based on reports at https://bitbucket.org/site/master/issues/4123/fatal-the-remote-end-hung-up-unexpectedly this sometimes helps, but it doesn't work consistently. – mc0e Mar 14 '17 at 05:46

Cloning with SSH instead of HTTP works for me. **With SSH I also see a performance increase while cloning** – Vishrant Jul 09 '20 at 02:02

My repository size is 70G .I'm use ssh already,but still got the same error – linjiejun Sep 21 '20 at 08:39

Could someone explain WHY this would be the solution? As a less experienced github user, this question and the one linked in the answer don't appear to have any connection. I'm hesitant to learn how to do this when there is no logical explanation of why switching to SSH would solve the problem of "remote end hung up unexpectedly" – canderson156 Oct 15 '20 at 13:44

caused this issue please help git@github.com: Permission denied (publickey) – Muhammad Tarique Feb 22 '21 at 02:11

In my case, this didn't solve the problem, however, it did bring the underlying error to the surface: `remote: fatal: pack exceeds maximum allowed size (2.00 GiB)`. For some reason, using HTTPS didn't provide that error message during the push and instead would only show `fatal: the remote end hung up unexpectedly`. – dev8675309 Mar 03 '22 at 15:23

this helped me when trying to clone on a very slow PC inside cygwin - it continued to remote end hung up - until I used this command – serup Apr 05 '17 at 21:52

This help me to resolve the "fatal: The remote end hung up upon initial contact" issue. – Karthic.K Jun 05 '17 at 04:53

It works! Thx. +1 – Adrián Feb 15 '22 at 14:51

This fixed my problem, but it also squashed the detached HEAD changes into a state where merging them became obnoxious (everything was converted to an ADD). I wish I had researched this one more before running it. – MatrixManAtYrService Jul 01 '16 at 03:40

This fixed my problem. My problem was (using ssh): $ git push | Enumerating objects: 886, done. | Counting objects: 100% (850/850), done. | Connection to bitbucket.org closed by remote host. | fatal: the remote end hung up unexpectedly | Compressing objects: 100% (831/831), done. | fatal: the remote end hung up unexpectedly – manuelpgs Sep 09 '20 at 02:58

Git will exec gc command automaticly before exec push command – linjiejun Sep 21 '20 at 08:45

@linjiejun in my case, I could not push until I pulled first, and the pull is where I was getting the error "fatal: Out of memory, malloc failed..." – brethvoice Jul 13 '21 at 15:36

Thank you! for the solution and plea. – Tom Aug 19 '21 at 12:33

ssh itself has some tuning options (keepalives etc) but the main tuning options are generally kernel-level and need to be set on both sides (e.g., over on GitHub as well). Kind of a problem. Something I'd like to see for cases like yours is an aggregator (LAGG interface style) that can use both the satellite and the cell phone networks. This is unfortunately far from trivial. – torek Nov 18 '21 at 07:12

One can use `git remote set-url origin https://github.com/user/repo`. No need to remove first – Maicon Mauricio Aug 05 '21 at 12:35

Great! Thank you! – TheGabornator Oct 14 '21 at 08:19

In this answer, `http.postBuffer` is effectively set to 150 MiB. If necessary, one can go higher up to 2 GB as I try to explain in my [answer](https://stackoverflow.com/a/64565533/). – Asclepius Oct 28 '20 at 02:22

SSH config just fixed my problem with gitlab.com. Thank you a lot. – Alberto Jan 23 '21 at 20:49

How do I do this for GitHub? Is my host github.com? – Giovanni May 09 '21 at 08:41

Thanks for the note. I'm facing the same issue. It seems that something (firewall?) on the local (wifi) network might somehow break the connection to git servers. The connection is otherwise really good here, so I suspect it might be configuration issue on the (MikroTik) router. – kub1x Apr 09 '21 at 12:55

can you explain how to split the commit? – arilwan Feb 22 '22 at 19:07

@arilwan In my case, there were 5 or 10 files, if I recall correctly, so I committed the first half and pushed it, then committed the second half and pushed that. It went through instantly both times. – user11809641 Feb 23 '22 at 02:40

we have a beta ansible workflow and rebuilding the site caused exactly this, cloning the repo on top of the other one. Ansible thing to fix but casing a git problem. Thanks :-) – Alejandro Moreno Mar 24 '16 at 10:33

I thought I included all relevant info - it's caused by a case mismatch. I've added a sentence to be more explicit, but this isn't really about the link. Sorry if that wasn't clear. – Thomas Dec 03 '15 at 11:08

This work for me, thanks alot! – Hernando Abella Sep 22 '21 at 15:48

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Dec 02 '21 at 17:19

this is not a solution buddy! – Behrouz.M Jul 10 '16 at 06:38

I know this is not an ideal solution, but it solved the problem in my case. It can be still lifesaver when all the other answer fails, as they did in my case. – nopara73 Jul 11 '16 at 06:13

I also had this exact issue (migrating from TFS though). I upgraded from 2.19 to 2.20 and it was fixed, a cursory look through release notes didn't reveal what the issue might have been though. – George Richardson Jan 18 '19 at 09:04

I have just upgraded to 2.20.1.windows.1 and it still won't let me push to the remote repository – Vidar Feb 06 '19 at 17:43

@Vidar May be check for large files, GitHub has a strict limit of 100MB https://help.github.com/articles/what-is-my-disk-quota/; Have a look at "Manually reviewing large files in your repository" section in https://confluence.atlassian.com/bitbucket/reduce-repository-size-321848262.html; the page itself is a good read. – Mahmoud Hanafy Feb 12 '19 at 22:21

@MahmoudHanafy - thanks - it was a parameter in the web.config about max file size - increase that and git behaves and everyone is happy! It's not GitHub for me but our own private on site Bonobo.Git.Server. – Vidar Feb 13 '19 at 18:04

What do you mean by "Git Shell"? Using `git` in a terminal? – Kalle Richter Feb 18 '17 at 19:42

Git, fatal: The remote end hung up unexpectedly

45 Answers45

Why this value?

Why not set lower?

Why not set higher?

Linked

Related