dev@local: ~/project — git
dev@local~/project$git status
fatal: remote end hung up unexpectedly
fatal: index-pack failed
Diagnostics Translation
The connection to the server was closed abruptly before Git finished transferring data.
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 transport failure means the remote conversation terminated mid-stream, after contact was established but before Git finished reading the exchange.

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

$Trying to push a massive 5GB repository in a single command over a slow network
Trying to push a massive 5GB repository in a single command over a slow network
$Cloning a monolithic repository that causes the remote server to run out of memory
Cloning a monolithic repository that causes the remote server to run out of memory

Technical Background

01

This error usually implies a resource exhaustion issue (timeout or buffer limit) rather than an authentication or configuration error.

02

Increasing Git's HTTP post buffer size or switching from HTTPS to SSH can sometimes bypass proxy-related hangups.

Underlying Causes

The repository size exceeds the server's timeout limit or memory capacity
A severe drop in internet connection quality during a large clone
An aggressive corporate proxy terminating long-running SSH/HTTPS connections

Frequently Asked Questions

No, Git transactions are atomic. If the push doesn't complete 100%, the remote repository remains unchanged.

Related Git States