Thanks for posting in the GitHub Community, @Kavita34612!

We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Discussions category is solely related to conversations around the GitHub product Discussions. This question should be in the Programming help category. I've gone ahead and moved it for you. Good luck!

Hi @Kavita34612 👋,

This is a fairly common issue when pushing large files using Git LFS, especially if your connection is unstable or if Git is not tuned for large payloads.

Here’s a full checklist and solution path to help ur resolve the error:

⸻

⚠️ Error Summary

RPC failed; curl 56 OpenSSL SSL_read: Connection was reset, errno 10054
fatal: the remote end hung up unexpectedly

This typically points to a timeout, buffer size, or connection reset during a large file transfer.

⸻

✅ Recommended Fixes

🔹 1. Increase Git Buffer Size

Run the following command to allow larger files to be pushed:

git config --global http.postBuffer 524288000 // code in terminal

👉 This sets the buffer to 500MB, which is often enough for large LFS pushes.

⸻

🔹 2. Disable LFS Batch Mode (Optional Fix)

Some Git hosting services have issues with LFS batch mode:

git config --global lfs.batch false // code in terminal

⸻

🔹 3. Use HTTPS Over SSH (If Applicable)

If you’re using HTTPS, try switching to SSH:

git remote set-url origin git@github.com:username/repo.git. // code in terminal

This avoids many SSL-related issues.

⸻

🔹 4. Try Chunked Uploads (GitHub Only)

If you’re using GitHub, enable LFS transfer via basic instead of batch:

git config --global lfs.transfer.maxretries 10
git config --global lfs.concurrenttransfers 3
git config --global lfs.transfer.allowinsecure true

⸻

🔹 5. Check for Firewalls or Antivirus
• Corporate networks or Windows Defender can interrupt large SSL reads.
• Try disabling antivirus temporarily and use a personal or different Wi-Fi if available.

⸻

🔹 6. Try Smaller Commits

Break your push into smaller chunks:

git add bigfile1
git commit -m "Push part 1"
git push

git add bigfile2
git commit -m "Push part 2"
git push

⸻

Let me know how it goes — happy to help further if the issue persists! 😊

Git LFS Push Error Troubleshooting Guide

This guide helps resolve the common error when pushing large files using Git LFS:

error: RPC failed; curl 56 OpenSSL SSL_read: Connection was reset, errno 10054  
fatal: the remote end hung up unexpectedly

This is usually caused by network timeouts, Git buffer limits, or exceeding GitHub LFS quotas.

Common Causes

• Large files exceeding Git buffer limit
• Unstable or slow internet connection
• Exceeding GitHub LFS storage or bandwidth quota
• Firewall, antivirus, or proxy interference
• Pushing too many large files at once

Solutions

1. Increase Git HTTP Buffer Size

Increase the buffer to 500MB:

git config --global http.postBuffer 524288000

2. Disable Git LFS Batch Mode

This sometimes improves upload reliability:

git config --global lfs.batch false

3. Push Over SSH Instead of HTTPS

Switch remote to SSH:

git remote set-url origin git@github.com:USERNAME/REPO.git
git push origin main

Replace USERNAME/REPO with your GitHub repo path.

4. Push in Smaller Chunks

Avoid pushing all files at once:

git add largefile1.zip
git commit -m "Add largefile1"
git push

5. Use a More Stable Network

• Use wired Ethernet or better Wi-Fi
• Try a mobile hotspot
• Use a VPN if throttling is suspected

6. Check Firewall/Antivirus

Temporarily disable firewall/antivirus or configure proxy settings if applicable.

7. Check GitHub LFS Quota

GitHub free-tier limits:

• 1 GB LFS storage
• 1 GB/month bandwidth

Check usage: https://github.com/settings/billing

Retry Push After Applying Fixes

git lfs install
git add .
git commit -m "Retrying large file push"
git push origin main

Summary Checklist

• Increased HTTP buffer
• Disabled LFS batch mode
• Switched to SSH
• Pushed files in chunks
• Checked network stability
• Checked antivirus/firewall
• Verified LFS quota