dev@local: ~/project — git
dev@local~/project$git status
fatal: rpc failed curl
fatal: index-pack failed
Diagnostics Translation
The underlying HTTP client (cURL) failed to complete the network request.
waiting for resolution...
MediumVersion Control System

Reviewed for reference consistency: April 11, 2026

Code is Safe

SECURE

Git has paused the operation to protect your code. No data has been lost or corrupted.

What To Know

This points to HTTP transport failure while Git was moving pack data, not to a branch-logic or merge-state problem.

Where Did It Fail?

Working Tree
Your local files
add
Staging Index
Prepared changes
commit
Local Repo
Commit history
push/fetch
Remote Server
GitHub/GitLab
The error occurred during a network exchange. Your local files are untouched, but Git cannot reach the remote server.

Commands That Trigger This

$Pushing a repository that contains large binary files over HTTPS
Pushing a repository that contains large binary files over HTTPS
$Cloning an enterprise repository while connected to a strict corporate proxy
Cloning an enterprise repository while connected to a strict corporate proxy

Technical Background

01

HTTP was originally designed for small stateless requests, not streaming massive binary packs. Git works around this, but strict proxies often break the connection.

02

Adjusting Git's `http.postBuffer` configuration or cloning via SSH (which avoids cURL entirely) are common workarounds.

Underlying Causes

Pushing a commit containing files larger than the `http.postBuffer` limit
Unstable VPN or proxy terminating the HTTP connection mid-transfer
Server-side rate limiting rejecting the payload

Frequently Asked Questions

Because HTTPS uses cURL and strict HTTP buffering rules, while SSH opens a raw persistent socket that is much more tolerant of large data streams.

Related Git States