fatal: the remote end hung up unexpectedly
The Git server closed the connection
Seen in git clone, fetch, pull and push over HTTPS or SSH
The other end closed the connection in the middle of a git operation; the real reason is usually in the line printed just before it.
Common causes
- A proxy or server size limit rejected a large push (look for RPC failed; HTTP 413 above it).
- The network or a firewall dropped a long transfer (look for RPC failed; curl 18 or 56).
- SSH authentication or access to the repository failed and the server disconnected.
How to fix it
- Read the error lines above this one and fix that cause first.
- Try the other transport (SSH instead of HTTPS, or the reverse) to see if one path is blocked.
- For big repositories, clone shallow (--depth 1) and fetch the rest later.
Got a different message? Paste it into the error explainer.
Related errors
- error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413 · The push is larger than the server or proxy accepts
- error: RPC failed; curl 18 transfer closed with outstanding read data remaining · The connection dropped during a git transfer
- kex_exchange_identification: Connection closed by remote host · The SSH server closed the connection before the handshake
- Permission denied (publickey) · The server rejected every SSH key you offered
- Host key verification failed. · SSH couldn't confirm the server's identity
- WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! · The server's SSH host key is different from last time
- Unable to negotiate with 203.0.113.10 port 22: no matching host key type found. Their offer: ssh-rsa · The server only offers an old host key type
- Unable to negotiate with 203.0.113.10 port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 · Client and server share no key exchange algorithm
- Received disconnect from 203.0.113.10 port 22:2: Too many authentication failures · The client offered too many keys before the right one
- Connection closed by 203.0.113.10 port 22 · The SSH server ended the session
- npm ERR! code ETIMEDOUT · npm couldn't reach the registry in time
- npm ERR! code ERR_SOCKET_TIMEOUT · The registry connection went silent