error: RPC failed; HTTP 400 curl 22 / curl 92 HTTP/2 stream was not closed cleanly — the remote end hung up unexpectedly
A large HTTPS push/clone broke mid-transfer — size limits, proxies or flaky HTTP/2.
Seen on:
Git
Meaning
Big pushes (large files or history) exceed proxy/server limits; HTTP/2 stream errors happen on some networks. The fix depends on whether it’s size or network.
Common causes
- Very large push (big files, many commits)
- Corporate proxy/antivirus interfering
- HTTP/2 issues
- Low http.postBuffer for older Git versions
⚡ Quick fix
- Push in smaller chunks or remove large files (use Git LFS)
- Try HTTP/1.1: git config --global http.version HTTP/1.1
- Use SSH instead of HTTPS
Detailed fix by platform
Git
git config --global http.version HTTP/1.1
How to diagnose
- Size — How big is the push?
- Network — Proxy/VPN?
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026