GitHub push not working (Connection Error)

Question

Hi I have an issue with GitHub when pushing. It started happening two days ago or so and I can't figure it out.

When pushing from terminal I get:

Counting objects: 358, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (322/322), done.
error: RPC failed; result=56, HTTP code = 200 15.52 MiB/s   
fatal: The remote end hung up unexpectedly
Writing objects: 100% (358/358), 157.16 MiB | 16.00 KiB/s, done.
Total 358 (delta 230), reused 3 (delta 3)
fatal: The remote end hung up unexpectedly
Everything up-to-date

Before throwing the fatal error it hangs for good three minutes. It says everything is up to date but evidently the changes aren't saved to github. I've pushed the same repository to bitbucket without any problems. I suspect it's some sort of timeout.

This is how my .git/config looks like.

[core]
    repositoryformatversion = 0
    filemode = true
    bare = false
    logallrefupdates = true
    ignorecase = false
    precomposeunicode = true
[branch "master"]
[remote "origin"]
        url = https://github.com/****/****.git
        fetch = +refs/heads/*:refs/remotes/origin/*
[remote "bitbucket"]
        url = https://***@bitbucket.org/****/***.git
        fetch = +refs/heads/*:refs/remotes/bitbucket/*

I've also tried to sync with the github app and it takes pretty long until it throws a "Network Error. Check your Internet connection and try again."

Thanks in advance.

Does stackoverflow.com/a/22005335/6309 or any of its comments would help? Or stackoverflow.com/a/29557970/6309 — VonC
– VonC, Commented Aug 16, 2015 at 8:43
I already tried the suggested config setting (because I saw it in several SO) but didn't have any luck. — yafrack
– yafrack, Commented Aug 16, 2015 at 9:09
Did you try the comments (like "disabling the Kaspersky AV NDIS 6 Filter" or the equivalent in your anti-virus)? Or the other suggestions in stackoverflow.com/a/29557970/6309? — VonC
– VonC, Commented Aug 16, 2015 at 9:10
I don't have any firewall on my mac to my knowledge. What's weird is that bitbucket and heroku works without a problem. — yafrack
– yafrack, Commented Aug 16, 2015 at 9:44
Any more clue with a do GIT_CURL_VERBOSE=1 git push? What git version are you using? — VonC
– VonC, Commented Aug 16, 2015 at 9:58

Community · Accepted Answer · 2017-05-23 11:58:00Z

2

This knowledge base page do mention:

Cause

Error code 56 indicates a curl receive error of CURLE_RECV_ERROR which means there was some issue that prevented the data from being received during the clone process.
Typically this is caused by a network setting, firewall, VPN client, or anti-virus that is terminating the connection before all data has been transferred.

Temporarily disable any firewall or anti-virus software and attempt the clone again.

Diagnosis

To turn on Git debug logging, before pushing using the command line, proceed like this for different OS:

On Linux
Execute the following in the command line before executing the Git command:

export GIT_TRACE_PACKET=1
export GIT_TRACE=1
export GIT_CURL_VERBOSE=1

On Windows
Execute the following in the command line before executing the Git command:

set GIT_TRACE_PACKET=1
set GIT_TRACE=1
set GIT_CURL_VERBOSE=1

Workaround

If the usual recommendations (like git config --global http.postBuffer 2M) fail:
Switch to ssh (after generating ssh keys):

git remote set-url orgin [email protected]:username/repo

edited May 23, 2017 at 11:58

CommunityBot

11 silver badge

answered Aug 16, 2015 at 10:10

VonC

1.4m569 gold badges4.8k silver badges5.7k bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

yafrack Over a year ago

You mention the error should be caused in the clone process but I'm indeed trying to push, not clone. Does this apply anyway? Thanks for the detailed answer

VonC Over a year ago

@marc yes, in both cases, clone or push, curl is involved.

yafrack Over a year ago

I tried the ssl and still get the error. Write failed: Broken pipe6/375), 53.94 MiB | 45.00 KiB/s fatal: The remote end hung up unexpectedly error: pack-objects died of signal 13 error: failed to push some refs to '[email protected]:***/***.git'

VonC Over a year ago

@marc then that means the content you are trying to push is not supported. Probably because you have a commit too big. Try rtyley.github.io/bfg-repo-cleaner

yafrack Over a year ago

Yeah I have some bins that are bigger than they should. I removed them but it's still complaining. I tried the cleaner but it didn't help.

|

Collectives™ on Stack Overflow

GitHub push not working (Connection Error)

1 Answer 1

Cause

Diagnosis

Workaround

6 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Cause

Diagnosis

Workaround

6 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related