Git Fatal: The remote end hung up unexpectedly [How to Solve]

When using git to update or submit a project, “fatal: the remote end hung up unexpectedly” appears because the pushed file is too large

That’s simple, either the cache is not enough, or the network is not good, or the wall is the reason

Especially when the resource pool is abroad. This problem may be caused by the network

Method 1:

Modify the commit cache size to 500m or larger

git config –global http.postBuffer 524288000

# some comments below report having to double the value:

git config –global http.postBuffer 1048576000

Or modify the generated config file under the. Git directory generated by clone/create version library and add it as follows:

[http]
postBuffer = 524288000

It is amended as follows:

Then push again

Method 2:

Configure the minimum speed and minimum speed time of GIT:

Git config — global http.lowspeedlimit 0
git config — global http.lowspeedtime 999999 unit second
— the global configuration is effective for the current user. If it needs to be effective for all users, use — system

Method 3:
fatal: the remote end hung up unexpected lyb | 2.00 KIB/s

Mine is like this, with | 2.00kib/s at the back

This sentence shows that the remote end is suspended | 2kib/s

It should be due to the wall that the network speed is too slow, and the project is a little too big to upload

Similar Posts: