Hello Guys, How are you all? Hope You all Are Fine. Today I am trying to send my projects via bash to the repo and suddenly I get the following error unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly in Github. So Here I am Explain to you all the possible solutions here.
Without wasting your time, Let’s start This Article to Solve This Error.
- How unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly Error Occurs ?
- How To Solve unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly Error ?
- Solution 1: For Windows
- Solution 2: For Linux/Mac
- Solution 3: committing with each addition
- Summery
How unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly Error Occurs ?
I am just trying to send my project to the repo by bash and I am facing the following error.
Enumerating objects: 27, done. Counting objects: 100% (27/27), done.
Delta compression using up to 16 threads Compressing objects: 100% (24/24), done.
Writing objects: 100% (25/25), 187.79 KiB | 9.39 MiB/s, done.
Total 25 (delta 1), reused 0 (delta 0), pack-reused 0
send-pack: unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly
How To Solve unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly Error ?
How To Solve unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly Error?
To Solve unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly Error If You are using the Windows Operating system then Just execute this command before executing the Git command. set GIT_TRACE_PACKET=1 set GIT_TRACE=1 set GIT_CURL_VERBOSE=1 Now your error should be not appearing.
Github – unexpected disconnect while reading sideband packet
To Solve unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly Error If You are using the Windows Operating system then Just execute this command before executing the Git command. set GIT_TRACE_PACKET=1 set GIT_TRACE=1 set GIT_CURL_VERBOSE=1 Now your error should be not appearing.
Solution 1: For Windows
If You are using the Windows Operating system then Just execute this command before executing the Git command.
set GIT_TRACE_PACKET=1
set GIT_TRACE=1
set GIT_CURL_VERBOSE=1

Then Try this command
git config --global core.compression 0
git clone --depth 1 <repo_URI>
# cd to your newly created directory
git fetch --unshallow
git pull --all
Solution 2: For Linux/Mac
If you are using Mac Or Linux Operating system then Just execute this command before executing the Git command.
export GIT_TRACE_PACKET=1
export GIT_TRACE=1
export GIT_CURL_VERBOSE=1
Then Try this command
git config --global core.compression 0
git clone --depth 1 <repo_URI>
# cd to your newly created directory
git fetch --unshallow
git pull --all
Solution 3: committing with each addition
- Just delete the .git folder
- then add a few files at a time or make change in your existing file.
- commit with each addition.
- Now your error should be not appearing.
Summery
It’s all About this issue. Hope all solution helped you a lot. Comment below Your thoughts and your queries. Also, Comment below which solution worked for you?
Also Read