Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How can I resolve fetch-pack: unexpected disconnect while reading sideband packet

Ruma Kumari
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 04, 2023

$ git clone https://innersource.*.com/*repoName.git
Cloning into 'repoName'...
remote: Enumerating objects: 2845, done.
remote: Counting objects: 100% (2845/2845), done.
remote: Compressing objects: 100% (2615/2615), done.
error: 2272 bytes of body are still expected | 2.14 MiB/s
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

1 answer

1 accepted

0 votes
Answer accepted
Victor Menes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 04, 2023

Hey Ruma,


Let's try to help you out here as I've seem some other users with the same issue.

In the past, I've seem below command being ran by the user received the error while trying to clone and it got resolved.


  • Let's try to resolve the issue by increasing buffer:
    git config --global http.postBuffer 52428800
  • Turn off the compression
    git config --global core.compression 0
  • Try the workaround here:
    $ git clone*repoName.git --depth 1
    $ cd repository
    $ git fetch --unshallow

Please let me know if that was helpful and if it resolved it :)

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events