GIT 推送失败 401 致命 - 带有 Git TFS 2017 upd1 的存储库 GIT [英] GIT push fails 401 fatal - Repository GIT with Git TFS 2017 upd1

问题描述

我在 GIT WebO (v1.8) 和 Git TFS2017 upd1 之间的通信中收到的错误取决于什么?错误信息如下:

What does the error i receive in communication between GIT WebO (v1.8) and Git TFS2017 upd1 depend on? The error message is as follows:

401 致命:远端意外挂断

401 fatal: The remote end hung up unexpectedly

除了 http.PostBuffer 和 Origin Url 之外，我还能检查什么???谢谢加布里埃尔

what can I check in addition to http.PostBuffer and Origin Url ??? Thank you Gabriele

推荐答案

您是否使用代理服务器?

Are you using proxy server?

Git 中的Smart HTTP"协议使用了Transfer-Encoding: chunked"包含大于 1MB 的打包对象时的 POST 请求尺寸.一些代理服务器，如 Nginx，不支持这种传输默认编码，请求在收到之前会被拒绝到藏匿处.因此，Stash 日志不会显示任何额外的信息.

The "Smart HTTP" protocol in Git uses "Transfer-Encoding: chunked" in POST requests when it contains packed objects greater than 1MB in size. Some proxy servers, like Nginx, do not support this transfer encoding by default, and the requests will be rejected before they get to Stash. Because of this, the Stash logs will not show any extra information.

无论如何，首先确保您有权限为存储库进行 git push.然后确保正确设置远程 URL:git remote set-url origin <new-url>

Whatever, firstly make sure you have the permission to git push for the repository. Then make sure set the remote URL correctly: git remote set-url origin <new-url>

然后尝试将 Git 缓冲区大小增加到存储库的最大单个文件大小:

Then try to increase the Git buffer size to the largest individual file size of your repo:

git config --global http.postBuffer 157286400

请参阅以下文章并按照解决方法和解决方案来解决此问题:Git Push失败 - 致命:远端意外挂断

Please refer to below article and following the workaround and solution to fix the issue: Git Push Fails - fatal: The remote end hung up unexpectedly

另一个类似的线程供您参考:Git - 错误:RPC 失败；result=22, HTTP code = 401 fatal: 远端意外挂断

Another similar thread for your reference: Git - error: RPC failed; result=22, HTTP code = 401 fatal: The remote end hung up unexpectedly

这篇关于GIT 推送失败 401 致命 - 带有 Git TFS 2017 upd1 的存储库 GIT的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！