Git "efrror: RPC failed; result=55, HTTP code = 0"推送

Question

我在这上面花了一整天，真的需要一些帮助。当我尝试推送一个相对较大的提交时，

Writing objects: 100% (21/21), 908.07 KiB | 0 bytes/s, done.
Total 21 (delta 17), reused 0 (delta 0)

git 需要很长时间才能响应然后给出

"efrror: RPC failed; result=55, HTTP code = 0 
atal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date"

我已经搜索了这个错误代码，最有可能的解决方案似乎是扩展缓冲区大小

git config http.postBuffer 524288000

我试过这个解决方案，但没有成功。在 VonC 的建议下，我尝试从 http 切换到 ssh。从 ssh，我在同一点挂了很长时间。最终出现如下错误信息

Read from remote host github.com: Connection reset by peer
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly

这可能是路由器问题吗？我曾尝试从不同网络上的不同计算机进行推送，并且能够成功完成此操作。

我离开了 Windows 主机上的 Linux 机器，并使用糟糕的 poshGit Windows PowerShell 界面。

有什么想法吗？？

Answer 1

您可以按照 BitBucket article 中的调试建议进行操作:

Specifically, the 'result=55' portion.
This is the error code coming from libcurl, the underlying library used in http communications with Git. From the libcurl documentation, a result code of 55 means:

CURLE_SEND_ERROR (55)
    Failed sending network data.

原因

This can be caused by a variety of network related issues or even the Bitbucket service itself. It essentially means that the connection was dropped unexpectedly. Things to check would be to attempt the push from a machine on a 'clean' network outside of any corporate firewalls or proxies. Check all proxy servers to ensure they are properly moving SSL data and are fully permitted to complete.

To help troubleshoot this issue, try running the push with the command

GIT_CURL_VERBOSE=1 git push

解决方法

If after checking all connections and proxy configurations the connection still fails consistently, please report the information above to support. Then switch to SSH. We have a guide to getting it setup for Git at Set up SSH for Git. If you should run into any configuration issues while setting up SSH, please refer to our SSH Troubleshooting guide.