Cloning repositories ends with "fatal: fetch-pack: invalid index-pack output"

[pevogam]

Select Topic Area

Question

Body

Hi all, already for days we cannot clone various repositories from Github (so far I haven't isolated this to specific repos) and get the following strange output:

git clone https://github.com//.git
Cloning into ''...
remote: Enumerating objects: 5471, done.
remote: Counting objects: 100% (1099/1099), done.
remote: Compressing objects: 100% (190/190), done.
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
error: 6670 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

Note that we have tried setting the git HTTP/1.1 version and we still get this a most of the time.

[pevogam]

The problem I had is that I have some hosts that can clone the repository from the same network and with the same git settings and other hosts that fail to do so. There is no significant change in the networking configuration or distance to gateway between the two hosts.

[gustaff-weldon]

We are experiencing the same problem in our Ci since last Friday

Fetching the repository
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +60d1a5c93b7909b3440758c0454795de33ba9e7a:refs/remotes/origin/ci-git-issues
  Error: error: 6374 bytes of body are still expected
  fetch-pack: unexpected disconnect while reading sideband packet
  Error: fatal: early EOF
  Error: fatal: fetch-pack: invalid index-pack output
  The process '/usr/bin/git' failed with exit code 128
  Waiting 18 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +60d1a5c93b7909b3440758c0454795de33ba9e7a:refs/remotes/origin/ci-git-issues
  Error: error: 3872 bytes of body are still expected
  fetch-pack: unexpected disconnect while reading sideband packet
  Error: fatal: early EOF
  Error: fatal: fetch-pack: invalid index-pack output
  The process '/usr/bin/git' failed with exit code 128
  Waiting 16 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +60d1a5c93b7909b3440758c0454795de33ba9e7a:refs/remotes/origin/ci-git-issues
  Error: error: 31[51](https://github.com/myorg/myrepo/actions/runs/12200498690/job/34036863529?pr=32104#step:3:56) bytes of body are still expected
  fetch-pack: unexpected disconnect while reading sideband packet
  Error: fatal: early EOF
  Error: fatal: fetch-pack: invalid index-pack output
  Error: The process '/usr/bin/git' failed with exit code 128

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[pevogam]

We still experience this issue and so far nothing has changed - our only solution so far is to clone a particular branch and only the top commit.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[pevogam]

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

I think I have provided as much information as I could so far and I am always open to provide more information if anyone requests it.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[MurugananthamB]

Hi @pevogam,

This error typically stems from network-level issues, especially with large repositories or unstable connections. Here’s a checklist of proven solutions that often resolve this:

🔧 1. Use HTTP/1.1 explicitly (you’ve tried, but good to confirm):

 git config --global http.version HTTP/1.1

📦 2. Increase Git buffer size (important for large repos):

 git config --global http.postBuffer 524288000

(That’s 500MB — adjust as needed.)

🧱 3. Use shallow clone to reduce payload (good for CI/CD or testing):

 git clone --depth=1 https://github.com/your/repo.git

🌐 4. Check your firewall/proxy/VPN setup:
Some corporate or ISP-level proxies can cut connections mid-stream. If you’re behind a proxy, try:

 git config --global http.proxy http://proxy-url:port

And test without it if possible.

📡 5. Try using SSH instead of HTTPS:
If you have SSH keys configured:

 git clone git@github.com:your/repo.git

This often bypasses low-level HTTP-related issues.

📁 6. Use a different network (hotspot, VPN, or ISP):
Some users reported cloning works fine on mobile hotspots or alternate networks — which suggests a throttling or proxy issue.

🧪 7. Advanced workaround – git partial clone:

 git clone --filter=blob:none --no-checkout https://github.com/your/repo.git

This avoids downloading all file content initially.

Let me know if it helps — or feel free to share specific repo URLs or logs for a deeper look! 👍

[pevogam]

Hi, for now the clones succeed again (without changing anything like the above) so let's close this as unexplained temporary fluke in github's cloning provisioning.

[msoutopico]

I know this issue is closed, but for the record, I'm getting this error today:

remote: Enumerating objects: 1764, done.
remote: Counting objects: 100% (1764/1764), done.
remote: Compressing objects: 100% (824/824), done.
error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8)
error: 6197 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

[pevogam]

Yes, very likely because this was never fully closed and it seems to happen sporadically from time to time :/

[king-11]

We encounter this issue while doing pull on repositories which were cloned using

• single-branch
• filter=blob:none

[GeorgeLxL]

I am so sorry, but I found this issue right now.
I tried to reboot my computer, delete project and retry to clone, and anything I can do.
But I couldn't clone it.