Fatal - The remote end hung up unexpectedly

This error can occur if the end-to-end connection is terminated by either network because of a network time out. Cloning a very large repository can take longer than the network will allow and if the network drops the connection before the clone is finished, this error can occur.

Network speed and repository size are to be carefully considered when first cloning. If you are cloning a repository that has more than 4 releases in the master branch alone, a shallow clone should be done to reduce the number of objects requested and reduce the time needed to establish a repository. After that, you can safely execute git pull commands: Shallow Cloning

Another possible workaround is to choose the San Diego URL from the repository instead of using our regional redirector, Every repository presents 2 URLs: Downloload from nearest regional server, Download from San Diego