git clone 出现错误 fatal: The remote end hung up unexpectedly
2017-04-21 19:00
525 查看
背景:
在gitlab上新开了一个项目,然后把本地的代码push上去了。之后需要在公司的测试服部署项目,就需要先从gitlab上git clone项目,但是神奇的一幕出现了,竟然失败了,无论是ssh 还是http都是失败,title的异常是ssh方式报出来的。本地试了下,完全没问题,都可以clone。但是登陆测试服clone就不行。解决办法:
让同事看了下,他说让我把git的版本更新一下,cetos的初始版本是1.7. 1,然后我就把git的版本更到了最新版2.2.1。更新的方法可以看我的上一篇文章。更新成功之后我发现clone时候又出现了新的异常,fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
这个是明显的权限问题,但是一时间我又没想明白到底哪的权限出错了。ps:本人刚接触git 不久。 然后我就换了http的登陆模式,发现竟然可以,然后我输入自己的邮箱和密码,成功的把项目代码从gitlab中clone了下来。
相关文章推荐
- git clone 遇到错误:fatal: The remote end hung up unexpectedly
- Git中push时出现错误fatal: The remote end hung up unexpectedly
- BAE使用git push出现错误:fatal: The remote end hung up unexpectedly
- git fatal: The remote end hung up unexpectedly 错误
- git初步使用之push 错误:fatal: The remote end hung up unexpectedly
- git clone error: RPC failed; result=52, HTTP code = 0 fatal: The remote end hung up unexpectedly
- git push错误;fatal: The remote end hung up unexpectedly
- git:解决git错误:fatal: The remote end hung up unexpectedly
- git push错误;fatal: The remote end hung up unexpectedly
- 【Mood-17】 github中在本地进行上传的时候出现ERROR: Repository not found. fatal: The remote end hung up unexpectedly
- Git, fatal: The remote end hung up unexpectedly
- Git Push出现the remote end hung up unexpectedly
- git提交报异常,fatal: The remote end hung up unexpectedly
- Git(GitHub) 005 添加SSH密钥 — 解决:Permission denied (publickey) fatal The remote end hung up unexpectedly
- Git - error: RPC failed; result=22, HTTP code = 401 fatal: The remote end hung up unexpectedly
- git fatal: the remote end hung up unexpectedly
- Git - error: RPC failed; result=22, HTTP code = 401 fatal: The remote end hung up unexpectedly
- Git push 报错 fatal: the remote end hung up unexpectedly
- git提交报异常,fatal: The remote end hung up unexpectedly
- Permission denied (publickey). fatal: The remote end hung up unexpectedly while pushing back to git