I am trying to clone a repo I worked on just fine until I made some pushes today, and it’s returning this.
remote: Enumerating objects: 7686, done.
remote: Counting objects: 100% (7686/7686), done.
remote: Compressing objects: 100% (6493/6493), done.
error: RPC failed; curl 56 OpenSSL SSL_read: Connection was reset, errno 10054
error: 1797 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
What I tried so far:
git config --global http.postBuffer 524288000git clone --depth 1 <repo_URL>- Reinstalled Git
My internet connection is very good, ran a speedtest and it went smooth.
CodePudding user response：
The error message “Connection was reset” means that something, whether a program on your computer, your computer's network stack, or a system on the network, caused the connection to the remote system to be terminated unexpectedly. In technical terms, your connection received a TCP RST.
Sometimes this is an incidental network problem, and retrying will help, either immediately or at some point in the future. It can also be caused by an antivirus or firewall other than the default (the defaults are Windows Defender or Windows Firewall), a TLS MITM device, or another sort of proxy. If you're using any non-default antivirus or firewall, you should completely uninstall it, reboot, switch to the defaults, and then try again. Note that disabling it is often not enough to prevent this kind of breakage from occurring.
If you're using a TLS MITM device or other proxy, try accessing things from a different network and see if the problem persists. If it does not, contact your network administrator and inform them that their software is broken and must be fixed.
Note that as outlined in the Git FAQ, you should not need to set http.postBuffer at all and having to set it indicates a serious misconfiguration in your network configuration or on the remote server, in addition to wasting a large amount of memory. It also has absolutely no effect on clones or fetches, so you should completely remove that configuration.
CodePudding user response：
Wish I had a better explanation, but I retried cloning yesterday evening and it finally worked.