How to fix error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8) in Git

The most common and effective fix is to configure Git to use HTTP/1.1, which avoids HTTP/2 stream issues:

git config --global http.version HTTP/1.1

This tells Git to fall back to HTTP/1.1 for all HTTPS operations. After setting this, retry your operation:

# Retry clone
git clone https://github.com/user/repo.git

# Or retry push
git push origin main

For large repositories or slow connections, increase the buffer size to allow larger data chunks:

# Increase buffer to 500MB
git config --global http.postBuffer 524288000

# Or for a more conservative 150MB
git config --global http.postBuffer 157286400

This is often used in combination with the HTTP/1.1 fix for best results.

For large repositories, clone with minimal history first, then fetch the rest:

# Clone with only the latest commit
git clone --depth 1 https://github.com/user/repo.git

# Navigate into the repository
cd repo

# Fetch remaining history in smaller chunks
git fetch --unshallow

If --unshallow also fails, fetch history incrementally:

git fetch --depth=100
git fetch --depth=500
git fetch --unshallow

SSH connections don't use HTTP/2 and may be more reliable, especially behind proxies:

# Generate SSH key if you don't have one
ssh-keygen -t ed25519 -C "[email protected]"

# Add SSH key to ssh-agent
eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_ed25519

# Copy public key and add to GitHub/GitLab
cat ~/.ssh/id_ed25519.pub

Add the public key to your GitHub/GitLab account settings, then clone using SSH:

git clone [email protected]:user/repo.git

If you're behind a proxy, it may be interfering with the connection. Try bypassing it temporarily:

# Check current proxy settings
git config --global --get http.proxy
git config --global --get https.proxy

# Unset proxy temporarily
git config --global --unset http.proxy
git config --global --unset https.proxy

If you need the proxy, ensure it's properly configured:

# Set proxy with authentication if needed
git config --global http.proxy http://username:[email protected]:8080

If you're on a slow connection, increase timeout settings:

# Prevent Git from timing out on slow connections
git config --global http.lowSpeedLimit 0
git config --global http.lowSpeedTime 999999

These settings tell Git to not abort even if data transfer is very slow.

Network issues are a common cause. Try these options:

- Disconnect VPN: VPNs can add latency and cause instability
- Switch to mobile hotspot: Test if your regular network is the issue
- Use wired connection: If on WiFi, try Ethernet
- Retry at different time: Server load may vary throughout the day

After changing networks, retry your Git operation.

Security software can intercept and modify HTTPS traffic:

Windows:
- Temporarily disable antivirus real-time protection
- Add Git and your repository folder to exclusions

macOS:
- Check System Preferences > Security & Privacy for any security tools

Corporate environments:
- Contact IT about HTTPS inspection or TLS interception policies
- Request an exception for git operations

Always re-enable security software after testing.

If the above fixes don't work or cause other issues, reset to defaults:

# Remove custom HTTP settings
git config --global --unset http.version
git config --global --unset http.postBuffer
git config --global --unset http.lowSpeedLimit
git config --global --unset http.lowSpeedTime

Then try a combination approach with fresh settings.