I have been using a Git repository for a couple years and still feel like a newb.. help is most welcome!
It starts cloning for a while:
remote: Counting objects: 22394<br>
remote: Compressing objects: 100% (12314/12314)<br>
Receiving objects: 32% ....
The error:
error: RPC failed; result=56, HTTP code = 200<br>
fatal: The remote end hung up unexpectedly<br>
fatal: early EOF<br>
fatal: index-pack failed
The git command:
git clone https://[username]:[password]@github.com/MegaWorldStudios/OmegatechV2.git "C:\OmegatechV2"
Git Version:
1.9.4-preview20140929 (downloaded/updated today from the git fellas)
I found questions such as this one, but none of the answers solves the problem.
I've also tried:
Setting the postBuffer higher as mentioned from similar posts
git config http.postBuffer 524288000<br>
git config --global http.postBuffer 524288000
Setting --depth 1 and doing a shallow clone that I can later pull the rest
Setting --depth 2
error: RPC failed; result=18, HTTP code = 200
Cloning from a branch other than the main branch
Reinstalling the software and updating
What does this infernal error mean and what's the fix/workaround?
Thanks so much in advance!
Usually, this means that either the source server could not locate the server in DNS or the RPC interface on the destination server is not working.
Type git clone , and then paste the URL you copied earlier. Press Enter to create your local clone. $ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY > Cloning into `Spoon-Knife`... > remote: Counting objects: 10, done. >
The Git clone command will create a new local directory for the repository, copy all the contents of the specified repository, create the remote tracked branches, and checkout an initial branch locally. By default, Git clone will create a reference to the remote repository called origin .
This error occurs due to Git's HTTPS protocol. To view the error in detail, you can set the GIT_CURL_VERBOSE
environment variable. For example:
$ GIT_CURL_VERBOSE=1 git pull
Your Antivirus or Firewall could be modifying the HTTP packets in transit. See git clone failed due to antivirus for example.
Finally, it could be an unreliable network connection. I am using an OSX machine connected to Wifi, and the problem disappeared when I switch to a LAN connection.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With