blocks|key|1790624|text|为解决这一问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1790625|用openssl而不是gnutls重建git解决了我的问题。|offset|length|style|BOLD|1790626|我跟着这些指示|1790627|entityMap|0|LINK|mutability|MUTABLE|url|http://devopscube.com/gnutls-handshake-failed-aws-codecommit/^0|0|1|7|B|6|0|3|4|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]|$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

To solve this issue:

Rebuilding git with openssl instead of gnutls fixed my problem.

I followed <a href="http://devopscube.com/gnutls-handshake-failed-aws-codecommit/" rel="noreferrer">these instructions</a>

blocks|key|1297251|text|来自@harlequin的公认答案可能有效，但我花了2个小时，无法从源代码构建git包。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1297252|然而，检查下面的链接，因为这是为我工作。|1297253|当git克隆时，远程终端意外挂起。|offset|length|1297254|只需更新http+post缓冲区值即可。|1297255|git+config+--global+http.postBuffer+1048576000|code-block|syntax|javascript|1297256|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/6842687/the-remote-end-hung-up-unexpectedly-while-git-cloning^0|0|0|0|H|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$F|Z|G|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

The accepted answer from @harlequin might work, but I spend 2 hours and could not build git package from source code.

However, Check the below link as this works for me. 

<a href="https://stackoverflow.com/questions/6842687/the-remote-end-hung-up-unexpectedly-while-git-cloning">The remote end hung up unexpectedly while git cloning</a>

just update the http post buffer value

<pre><code>git config --global http.postBuffer 1048576000
</code></pre>

blocks|key|1790923|text|在看了你的帖子后，我简单地通过|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1790924|apt+install+gnutls-bin|code-block|syntax|javascript|1790925|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

After reading your posts, I solved it simply by 

<pre><code>apt install gnutls-bin
</code></pre>

blocks|key|2545155|text|如果您需要克隆或拉动，我有一个解决方案--，问题在于存储库历史记录的大小。这也可能会有帮助，当你想推动以后，没有保证。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2545156|只需使用--depth=[number+of+last+commits]检索最后一次提交即可。|CODE|2545157|您可以在克隆时执行此操作，如果在添加了远程的本地存储库中工作，则可以在拉时执行。例如，只检索(每个分支的)最后一次提交：|2545158|git+clone+repo+--depth=1
#+or
git+pull+--depth=1|code-block|syntax|javascript|2545159|更新:如果遥控器在你面前的太多，问题可能会回来晚些时候，你试图拉动最后的变化，但有太多，连接关闭与curl+56。您可能必须使用git+pull+--depth=[number+of+commits+ahead+on+remote]，如果您正在处理一个非常活跃的存储库，这是很乏味的。|2545160|entityMap^0|F|6|0|4|W|0|0|0|1S|1G|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|Z|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|10|8|@]|D|@]|E|$N|O]]|$1|P|3|Q|5|6|7|11|8|@$9|12|A|13|B|H]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|S|$]]

I have a workaround if you need to clone or pull and the problem lies in the size of the repository history. It may also help when you want to push later, with no guarantee.

Simply retrieve the last commits with <code>--depth=[number of last commits]</code>.

You can do this at clone time, or, if working from a local repository to which you added a remote, at pull time. For instance, to only retrieve the last commit (of each branch):

<pre><code>git clone repo --depth=1
# or
git pull --depth=1
</code></pre>

UPDATE: if the remote is getting too much ahead of you, the issue may come back later as you try to pull the last changes, but there are too many and the connection closes with curl 56. You may have to <code>git pull --depth=[number of commits ahead on remote]</code>, which is tedious if you're working on a very active repository.

blocks|key|2544916|text|您可以设置一些选项来解决该问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2544917|无论是在全局级别：(需要如果您clone，不要忘记重置后)|offset|length|style|CODE|2544918|$+git+config+--global+http.sslVerify+false
$+git+config+--global+http.postBuffer+1048576000|code-block|syntax|javascript|2544919|或者在本地存储库上|2544920|$+git+config+http.sslVerify+false
$+git+config+http.postBuffer+1048576000|2544921|entityMap^0|0|F|5|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

You can set some option to resolve the issue

Either at global level: (needed if you <code>clone</code>, don't forget to reset after) 

<pre><code>$ git config --global http.sslVerify false
$ git config --global http.postBuffer 1048576000
</code></pre>

or on a local repository

<pre><code>$ git config http.sslVerify false
$ git config http.postBuffer 1048576000
</code></pre>

blocks|key|1790745|text|我还使用了基于Ubuntu的系统(+mate+18)，从github克隆大型回购时得到了类似的问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1790746|对我来说，简单的解决方案是使用ssh协议，而不是http(s)协议。|BOLD|1790747|e.g|1790748|git+clone+git@github.com:xxx/yyy.git|code-block|syntax|javascript|1790749|entityMap^0|7|6|0|F|3|O|7|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|H]|$9|X|A|Y|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|Z|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|10|8|@]|D|@]|E|$N|O]]|$1|P|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|Q|$]]

I am also using <code>Ubuntu</code> based system (Mint mate 18), got the similar issue when clone large repo from github.

The simple solution worked for me is to use ssh protocol instead of http(s) protocol.

e.g

<pre><code>git clone git@github.com:xxx/yyy.git
</code></pre>

blocks|key|1790664|text|我也遇到了同样的情况，重新启动系统解决了它:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1790665|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I also encountered same and restart of the system resolved it :)

blocks|key|1791050|text|WSL2用户可以通过Ubuntu18，阅读这篇文章获得这一信息。基本上你需要更新你的无线驱动程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1791051|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/microsoft/WSL/issues/4253^0|J|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

WSL2 users getting this with Ubuntu 18, <a href="https://github.com/microsoft/WSL/issues/4253" rel="noreferrer">read this</a>. 
Basically you need to update your wireless driver.

blocks|key|1300092|text|尝试升级openssl模块|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1300093|我通过这样做解决了它|1300094|sudo+apt+install+openssl|code-block|syntax|javascript|1300095|entityMap^0|4|7|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Try to upgrading <code>openssl</code> modules

I solved it by doing that

<pre><code>sudo apt install openssl
</code></pre>

blocks|key|1791255|text|我看到了类似的问题(尤其是深入地)在一些遗留项目，当我们克隆，过去生活在TFS上。实现长路解决了我们的问题，也许是值得尝试的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1791256|git+config+--system+core.longpaths+true|code-block|syntax|javascript|1791257|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I saw similar issues (particularly with depth) on some legacy projects when we were cloning that used to live on TFS. Enabling long paths resolved our issue and may be something else worth trying.
<pre><code>git config --system core.longpaths true
</code></pre>

blocks|key|1790901|text|当使用CppCheck克隆https时，我在Ubuntu18.04上遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1790902|的解决方案是使用，而不是使用http。|BOLD|1790903|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/danmar/cppcheck.git^0|D|5|3|8|0|0|0|8|E|4|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@$9|T|A|U|1|V]]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|H]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|I|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|J|$K|$5|L|M|N|E|$O|P]]]]

I faced this issue on Ubuntu 18.04 when cloning <a href="https://github.com/danmar/cppcheck.git" rel="nofollow noreferrer">CppCheck</a> using <code>https</code>.

A workaround to it was to use <code>http</code> instead.

blocks|key|1297472|text|我通过断开VPN解决了这个问题(我的操作系统是ubuntu16.04)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1297473|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I solved this problem by disconnecting my VPN (My OS is ubuntu-16.04).

blocks|key|2545105|text|我所做的就是切断和重新连接我的电脑从wifi和它的工作。有时候答案可能很简单。我的现在起作用了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2545106|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

All I did was disconnect and reconnect my pc from the wifi and it worked. Sometimes the answer might be very simple. Mine works now

blocks|key|1300353|text|对于Linux:+Simple，您可以在以下命令中运行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1300354|1)+git+config+-l
2)+git+config+--global+http.postBuffer+524288000
++++++++Or+set+double+value++1048576000
3)+git+config+--global+https.postBuffer+
4)+git+config+--global+core.compression+-1+
5)+service+apache2+restart|code-block|syntax|javascript|1300355|然后再次检查git的配置。|1300356|git配置-l|1300357|现在可以运行克隆命令了。|1300358|git克隆你的回购|1300359|我希望这个问题能得到解决。|1300360|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

For Linux:
Simple you can run below commands:
<pre><code>1) git config -l
2) git config --global http.postBuffer 524288000
 Or set double value 1048576000
3) git config --global https.postBuffer 
4) git config --global core.compression -1 
5) service apache2 restart
</code></pre>
Then again check the config of git
git config -l
now you can run clone command
git clone yourrepo
I hope this will be solved the issue.

blocks|key|1297396|text|检查您的网络是否正确，working...this问题也因互联网问题而发生|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1297397|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Check your Network is properly working...this problem also occures because of internet issues

blocks|key|2545192|text|我只是通过使用SSH克隆来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2545193|为此，我必须将机器的SSH密钥添加到我的帐户中。|2545194|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I just managed to solve this by cloning using SSH.

To do that I had to add my machine's SSH key to my account.

blocks|key|2545236|text|此外，在命令行中使用任何代理时可能会发生此错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2545237|如果您之前导出任何代理，请取消它。|2545238|$+unset+all_proxy+&&+unset+ALL_PROXY|code-block|syntax|javascript|2545239|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Additionally,this error may occurs in you are using any proxy in command line. 

if you export any proxy before , unset it .

<pre><code>$ unset all_proxy &amp;&amp; unset ALL_PROXY
</code></pre>

blocks|key|2545604|text|我只运行一个命令就解决了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2545605|apt升级(作为根用户)|blockquote|2545606|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|H|8|@]|9|@]|A|$]]|$1|E|3|-4|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

I solved it by just running single command
<blockquote>
apt upgrade (being root user)
</blockquote>

blocks|key|2544987|text|另一种方法是:请再试一次，有时它的发生只是因为你的网络状态。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2544988|我的情况如下。|2544989|​|2544990|📷|atomic|offset|length|2544991|2544992|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/2ad5a3663719387a06b914b300dc4c43.png|imageAlt^0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@$I|Y|J|Z|1|10]]|A|$]]|$1|K|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

Another way here：please try it again, sometimes it happen just result from your network status.
My situation is as below.
<a href="https://i.stack.imgur.com/TrG3R.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/TrG3R.png" alt="enter image description here" /></a>

blocks|key|1300198|text|尝试为此禁用您的IPV6，然后禁用。我觉得这是你的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1300199|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Try to disable your IPV6 for that and disable after. I think this is your problem.

blocks|key|2545291|text|我尝试了以上所有的方法，但都没有成功。最后，我意识到我有一个弱的WiFi连接，因此下载速度缓慢。我通过以太网连接我的设备，这立即解决了我的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2545292|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I tried all the above without success. Eventually I realised I had a weak WiFi connection and therefore slow download speed. I connected my device VIA Ethernet and that solved my problem straight away.

blocks|key|1297455|text|当我试图把一个新的分支推向上游时，我犯了这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1297456|git+push+--set-upstream+origin+xyz|code-block|syntax|javascript|1297457|我尝试了上面建议的几乎所有的git配置编辑，包括一个系统重新启动。什么都没用。|1297458|于是我回到师父那里，拉了拉，回到了我的xyz分支，和师父合并了一次，然后就能推开了。|1297459|*+currently+on+branch+xyz
git+checkout+master
git+pull
git+checkout+xyz
git+merge+master
git+push+--set-upstream+origin+xyz|1297460|我不得不说，师父与我在我的新分支"xyx“中的任何变化都没有冲突。只有来自master的几个新提交被合并到我的"xyz“分支。在正常的日子里这不应该是个问题。|1297461|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I got this error while i tried to push a new branch upstream

<pre><code>git push --set-upstream origin xyz
</code></pre>

I tried almost all of the git config edits suggested above including a system reboot. Nothing worked. 

So I went back to master and did a pull, went back to my xyz branch, did a merge with master and was able to push.

<pre><code>* currently on branch xyz
git checkout master
git pull
git checkout xyz
git merge master
git push --set-upstream origin xyz
</code></pre>

I have to say nothing in master conflicted with any of my changes in my new branch "xyx". Only a couple of new commits from master were merged to my "xyz" branch. This shouldn't have been a problem on normal days.

blocks|key|1791195|text|在nginx和克隆背后托管Git+Server也有同样的问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1791196|remote:+Enumerating+objects:+103,+done.+remote:+Counting+objects:+100%25+(103/103),+done.+remote:+Compressing+objects:+100%25+(47/47),+done.+remote:+Total+103+(delta+52),+reused+99+(delta+51),+pack-reused+0+Receiving+objects:+100%25+(103/103),+11.56+KiB+%7C+1.16+MiB/s,+done.+Resolving+deltas:+100%25+(52/52),+done.+error:+RPC+failed;+curl+56+GnuTLS+recv+error+(-110):+The+TLS+connection+was+non-properly+terminated.|offset|length|style|CODE|1791197|在搜索基于RPC的问题之后，似乎需要使用HTTP2。|1791198|因此，在我的nginx站点配置中，这一行：|1791199|listen+443+ssl;+#+managed+by+Certbot|1791200|被更改为此，以启用http2+-这不是默认的：|1791201|listen+443+ssl+http2;+#+managed+by+Certbot|1791202|总的来说，TLS似乎更快乐(例如，在检查详细输出时，我还犯了与curl和TLS有关的其他错误)。|1791203|我已经通过删除http2来验证这是一个根本原因，它会复制错误并恢复http2解决了这个问题。|1791204|entityMap^0|0|0|BA|0|0|0|0|10|0|0|0|16|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|16|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1A|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1B|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|W|$]]

Had the same problem hosting Go Git Server behind nginx and cloning:
<code>remote: Enumerating objects: 103, done. remote: Counting objects: 100% (103/103), done. remote: Compressing objects: 100% (47/47), done. remote: Total 103 (delta 52), reused 99 (delta 51), pack-reused 0 Receiving objects: 100% (103/103), 11.56 KiB | 1.16 MiB/s, done. Resolving deltas: 100% (52/52), done. error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was non-properly terminated. </code>
After searching RPC based issues, there appears to he a requirement to use HTTP2
Therefore this line in my nginx site configuration:
<code>listen 443 ssl; # managed by Certbot</code>
Was changed to this, to enable http2 - which is not a default:
<code>listen 443 ssl http2; # managed by Certbot</code>
And TLS in general seems happier (i.e. I had other errors regarding curl and TLS, when inspecting verbose output)
I have verified this as a root cause by removing http2, which reproduces the error and reinstating http2 resolves the problem.

blocks|key|1300325|text|我也有过类似的错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1300326|错误:+RPC失败；curl+56+GnuTLS+recv错误(-9)：接收到一个长度意外的TLS数据包。|1300327|当试图从Github克隆存储库时。|1300328|在尝试了这里发布的大多数解决方案后，这些解决方案都不起作用，结果证明这是父母对我们家庭网络的控制。关闭这些父母的控制解决了问题。|1300329|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I had a similar fault:
error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected length was received.
when trying to clone a repository from Github.
After trying most of the solutions posted here, none of which worked, it turned out to be the parental controls on our home network. Turning these parental controls off solved the problem.

blocks|key|2545500|text|如果您正在运行git服务器服务，那么它不是git客户机问题.也许这也是一个git服务器问题！这就是解决方案对我来说..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2545501|我们运行的是一个带有https前端nginx反向代理的gitbucket服务器。|2545502|在一个主要的系统OS版本升级之后，我们开始在所有git客户机上得到这个错误。原来，nginx被替换了，新包的默认nginx.conf也被安装了。默认的nginx用户'www-data‘已经不是以前的样子了。|2545503|在这一切背后的某个地方，一定有一个权限问题，因为将nginx用户重新设置为它以前的值，然后重新启动nginx使一切重新开始。……算了吧！(是的，在解决这个问题的单一改变之前，我已经多次重新启动了nginx+)。|2545504|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

If you are are running the git server service, then rather than it be a git client issue ... perhaps it's a git server issue too !
This is what the solution was for me...
We were running a gitbucket server with a front-end nginx reverse proxy for https.
Following a major system OS version upgrade, we started getting this error across all git clients.
Turns out that nginx got replaced and the new package's default nginx.conf got installed.
The default nginx user 'www-data' was NOT what it used to be.
Somewhere underneath it all, there must have been a permissions issue, because resetting the nginx user back to it's former value, and restarting nginx got everything going again. .... go figure ! (Yes I had restarted nginx many times prior to the one singular change that solved it)

blocks|key|2545541|text|自昨天以来，我一直面临着同样的问题，但现在已经成功地解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2545542|首先，删除git包和任何其他依赖的包。|2545543|$+sudo+apt-get+remove+git|code-block|syntax|javascript|2545544|然后安装git|2545545|sudo+apt-get+install+git-all|2545546|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I am facing the same issue since yesterday, but now successfully solved that issue.
First, remove the git package and any other dependent package
<pre><code>$ sudo apt-get remove git
</code></pre>
and then install git
<pre><code>sudo apt-get install git-all
</code></pre>

blocks|key|2545653|text|在我的例子中，问题在于我使用的是https而不是git协议。在我的配置文件中，我强迫git使用https。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2545654|[url+"https://"]
++++++++insteadOf+=+git://|code-block|syntax|javascript|2545655|通过从我的配置中删除它，我能够克隆所需的存储库。|2545656|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In my case the problem was that i was using the https instead of the git protocol.
In my config file I forced git to use https.
<pre><code>[url &quot;https://&quot;]
 insteadOf = git://
</code></pre>
By removing this from my config I was able to clone the required repository.

blocks|key|1300436|text|如果上面的所有答案都不适用于您，您应该检查以前是否启用过任何类型的代理：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1300437|git+config+--global+http.proxy+""|code-block|syntax|javascript|1300438|entityMap^0|X|2|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

If all answers above are not working for you, you should check if you've enabled any kind of proxy before :
<pre><code>git config --global http.proxy &quot;&quot;
</code></pre>

blocks|key|1791155|text|我的mac被连接到2.5GHZ的网络，我不得不启用我的wifi到5+5GHz。问题就消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1791156|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My mac was connected to a 2.5GHZ network, I had to enable my wifi to 5GHz. And the problem disappeared.

blocks|key|2545506|text|这解决了我的问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2545507|$+git+config+http.sslVerify+false
$+git+config+http.postBuffer+1048576000|code-block|syntax|javascript|2545508|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This solved my problem
<pre class="lang-sh prettyprint-override"><code>$ git config http.sslVerify false
$ git config http.postBuffer 1048576000
</code></pre>

blocks|key|1300400|text|原来我在一个防火墙后面，不允许访问Github，我通过联系我的ISP和禁用病毒保护来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1300401|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Turns out I was behind a firewall that didn't allow access to Github, I solved this by contacting my ISP and disabling virus protection.

blocks|key|2545057|text|简单地执行命令|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2545058|git+init|code-block|syntax|javascript|2545059|在克隆人帮我解决之前。|2545060|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Simply executing command

<pre><code>git init
</code></pre>

before cloning resolved it for me.

blocks|key|1790767|text|重新安装git将解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1790768|sudo+apt-get+remove+git
sudo+apt-get+update
sudo+apt-get+install+git|code-block|syntax|javascript|1790769|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Reinstalling git will solve the problem.

<pre><code>sudo apt-get remove git
sudo apt-get update
sudo apt-get install git
</code></pre>

I use Ubuntu 16.04. When I want to git push origin master I get:
<pre><code>error: RPC failed; curl 56 GnuTLS recv error (-12): A TLS fatal alert has been received.
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date
</code></pre>

How to fix git error: RPC failed; curl 56 GnuTLS

33 天实现自己的 AI 进化论？发文瓜分机械键盘、耳机等万元奖池！点击参加活动：<a href="https://cloud.tencent.com/developer/article/2503022" target="_blank">https://cloud.tencent.com/developer/article/2503022</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/01543e0407db10898a7ee9f420794432.jpg"/>

技术创作特训营有奖征文

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云AI代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

文章&问答评论现已支持表情

我用Ubuntu 16.04。当我想推原主时，我得到：error: RPC failed; curl 56 GnuTLS recv error (-12): A TLS fatal alert has been received.fatal: The remote end hung up unexpectedlyfatal: The remote end hung up unexpectedlyE

问如何修复git错误: RPC失败；curl 56 GnuTLS
EN

回答 33

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修复git错误: RPC失败；curl 56 GnuTLSEN

回答 33

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修复git错误: RPC失败；curl 56 GnuTLS
EN