Git，致命：远端意外挂断 [英] Git, fatal: The remote end hung up unexpectedly

问题描述

当我试图运行

  git push origin master --force 
  
  
 
 
我刚刚得到了
 
 pre $ 计数对象：2649，完成。 
使用多达2个线程的增量压缩。 
压缩对象：100％（1280/1280），完成。 
错误：RPC失败;结果= 22，HTTP代码= 413 | 116 KiB / s 
致命：远端意外挂断
写作对象：100％（2504/2504），449.61 MiB | 4.19 MiB / s，完成。 
共计2504（增量1309），重用2242（增量1216）
致命：远程端意外挂断
一切最新
  

这是否与安全有关？我试图创建一个公钥，如致命的答案：远程端挂断意外地并且再次运行它，但它仍然不起作用。我实际上没有使用钥匙吗？如果是这样，我该如何使用它？

解决方案

这看起来类似于如何让github默认为ssh而不是https for new库的。
可能值得尝试从http协议切换到ssh：

  $ git remote add origin [e-mail] ：username / project.git 
  

When I tried to run

git push origin master --force

I just got

Counting objects: 2649, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (1280/1280), done.
error: RPC failed; result=22, HTTP code = 413 | 116 KiB/s   
fatal: The remote end hung up unexpectedly
Writing objects: 100% (2504/2504), 449.61 MiB | 4.19 MiB/s, done.
Total 2504 (delta 1309), reused 2242 (delta 1216)
fatal: The remote end hung up unexpectedly
Everything up-to-date

Is it something to do with not being secure? I tried creating a public key as in the answer for Fatal: The remote end hung up unexpectedly and running it again, but it still doesn't work. Am I not actually using the key? If so, how do I use it?

解决方案

This looks similar to How do I get github to default to ssh and not https for new repositories. Probably it's worth trying to switch from http protocol to ssh:

$ git remote add origin [e-mail]:username/project.git

这篇关于Git，致命：远端意外挂断的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！