git push fails: 'error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)' / 'send-pack: unexpected disconnect while reading sideband packet'. How do I fix it?

Cause: Git over HTTPS uses curl, which talks HTTP/2 to most hosts. Large pushes or slow and unstable connections can make a proxy, load balancer or VPN in the path reset the HTTP/2 stream, and the push fails with curl error 92. Very large commits (big binaries, a huge first push) and corporate proxies make it much more likely. How to check: - Retry with verbose output: GIT_TRACE_CURL=1 git push (or GIT_CURL_VERBOSE=1) shows where the connection dropped. - Check the size of what you are pushing: git count-objects -vH, and look for large files you didn't mean to commit. Fix (try in order): 1. Force HTTP/1.1 for Git: git config --global http.version HTTP/1.1 (or set it only for the one repository, without --global). This alone fixes most cases. 2. Push in smaller pieces, for example push older commits first (git push origin <older-commit>:refs/heads/<branch>), then the rest. 3. Keep large binaries out of Git: move them to Git LFS or remove them from history before pushing. 4. If the host supports it, push over SSH instead of HTTPS, which avoids the HTTP layer. 5. Upgrade Git and curl. Raising http.postBuffer (for example to 50 MB) only helps in some proxy setups; it is not a general fix and uses more memory. After: once the push succeeds you can remove the http.version setting if you only needed it once, and if you added LFS, confirm with git lfs ls-files that the large files are tracked by LFS. Sources: https://docs.gitlab.com/topics/git/troubleshooting_git/ https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpversion https://0xacab.org/riseup/0xacab/issues/61