I m facing this error when I try to clone a repository from GitLab GitLab 6 6 2 4ef8369 remote Counting objects 66352 done remote Compressing objects 100 10417 10417 done error RPC failed curl 18 transfer closed with outstanding read data remaining fatal The remote end hung up unexpectedly fatal early EOF fatal index-pack failed The clone is then aborted How can I avoid this

Usually it happen because of one of the below reasone Slow Internet Switching to LAN cable with stable network connection helps in many cases Avoid doing any parallel network intensive task while you are fetching Small TCP IP connection time out on Server side from where you are trying to fetch Not much you can do about All you can do is request your System Admin or CI CD Team responsible to increaseTCP IP Timeout and wait Heavy Load on Server Due to heavy server load during work hour downloading a large file can fail constantly Leave your machine after starting download for night Small HTTPS Buffer on Client machine Increasing buffer size for post and request might help but not guaranteed git config --global http postBuffer 524288000 git config --global http maxRequestBuffer 524288000 git config --global core compression 0

try this git config --global user name John Doe git config --global user email johndoe example com https git-scm com book en v2 Getting-Started-First-Time-Git-Setup this is work for me capture png

These steps are working for me cd dir git init git clone your Repository Url I hope that works for you too

Tried all of the answers on here I was trying to add cocoapods onto my machine I didn t have an SSH key so thanks Do Nhu Vy https stackoverflow com a 38703069 2481602 And finally used git clone https git coding net CocoaPods Specs git cocoapods repos master to finally fix the issue found https stackoverflow com a 50959034 2481602

you need to turn off the compression git config --global core compression 0 then you need to use shallow clone git clone --depth 1 lt url gt then most important step is to cd into your cloned project cd lt shallow cloned project dir gt now deopen the clone step by step git fetch --depth N with increasing N eg git fetch --depth 4 then git fetch --depth 100 then git fetch --depth 500 you can choose how many steps you want by replacing this N and finally download all of the remaining revisions using git fetch --unshallow upvote if it helps you

For me the issue was that the connection closes before the whole clone complete I used ethernet instead of wifi connection Then it solves for me

These steps worked for me using git instead of https

After few days today I just resolved this problem Generate ssh key follow this article https help github com articles generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent Declare it to Git provider GitLab what I am using GitHub Add this to local identity Then clone by command git clone username mydomain com my group my repository git And no error happen The above problem error RPC failed curl 18 transfer closed with outstanding read data remaining because have error when clone by HTTP protocol curl command And you should increment buffer size git config --global http postBuffer 524288000

It happens more often than not I am on a slow internet connection and I have to clone a decently-huge git repository The most common issue is that the connection closes and the whole clone is cancelled Cloning into large-repository remote Counting objects 20248 done remote Compressing objects 100 10204 10204 done error RPC failed curl 18 transfer closed with outstanding read data remaining fatal The remote end hung up unexpectedly fatal early EOF fatal index-pack failed After a lot of trial and errors and a lot of remote end hung up unexpectedly I have a way that works for me The idea is to do a shallow clone first and then update the repository with its history git clone http github com large-repository --depth 1 cd large-repository git fetch --unshallow

Changing git clone protocol to try for example this error happened when git clone https xxxxxxxxxxxxxxx you can try with git clone git xxxxxxxxxxxxxx maybe ok then

[git] error: RPC failed; curl transfer closed with outstanding read data remaining

Usually it happen because of one of the below reasone:

Slow Internet.

Switching to LAN cable with stable network connection helps in many cases. Avoid doing any parallel network intensive task while you are fetching.

Small TCP/IP connection time out on Server side from where you are trying to fetch.

Not much you can do about. All you can do is request your System Admin or CI/CD Team responsible to increaseTCP/IP Timeout and wait.

Heavy Load on Server.

Due to heavy server load during work hour downloading a large file can fail constantly.Leave your machine after starting download for night.

Small HTTPS Buffer on Client machine.

Increasing buffer size for post and request might help but not guaranteed

git config --global http.postBuffer 524288000

git config --global http.maxRequestBuffer 524288000

git config --global core.compression 0

Examples related to git

• Does the target directory for a git clone have to match the repo name? • Git fatal: protocol 'https' is not supported • Git is not working after macOS Update (xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools) • git clone: Authentication failed for <URL> • destination path already exists and is not an empty directory • SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443 • GitLab remote: HTTP Basic: Access denied and fatal Authentication • How can I switch to another branch in git? • VS 2017 Git Local Commit DB.lock error on every commit • How to remove an unpushed outgoing commit in Visual Studio?

Examples related to gitlab

• GitLab remote: HTTP Basic: Access denied and fatal Authentication • How can I switch to another branch in git? • HTTP Basic: Access denied fatal: Authentication failed • Getting permission denied (public key) on gitlab • Delete commit on gitlab • error: RPC failed; curl transfer closed with outstanding read data remaining • ssh : Permission denied (publickey,gssapi-with-mic) • Fix GitLab error: "you are not allowed to push code to protected branches on this project"? • Change Default branch in gitlab • How can I clone a private GitLab repository?