Git push在Visual Studio 2015中不起作用 [英] Git push not working in visual studio 2015

查看:72
本文介绍了Git push在Visual Studio 2015中不起作用的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的visual studio 2015在Git连接到BitBucket时可以很好地工作. 但是,当连接到私有Gitlab服务器时,我遇到了一个奇怪的问题: -我可以通过IDE(团队资源管理器)从gitlab服务器克隆存储库.我可以获取/拉取,每当尝试将本地提交同步到服务器时,都会收到错误消息(推送到远程存储库时遇到错误... 500 ...).显然,gitlab服务器返回500内部服务器错误. 但是,当我从团队资源管理器中打开命令行并发出"git push"命令时,没有错误,并且推送成功.

My visual studio 2015 works fine with Git connecting to BitBucket. However when connecting to a private Gitlab server, I have a weird problem: - I can clone a repo from the gitlab server via the IDE (Team explorer). I can fetch/pull, put whenever I try to sync a local commit to the server, I get an error (error encountered while pushing to the remote repository... 500...). Obviously the gitlab server returns a 500 internal server error. However when I open a command line from within team explorer and issue a 'git push', there are no errors and the push succeeds.

  • 团队资源管理器推送和命令行推送之间有区别吗?

  • Is there a difference between the team explorer push and the command line push?

有没有办法查看团队资源管理器在推送时发送到gitlab服务器的请求?

Is there a way to see what request team explorer sends to the gitlab server while pushing?

推荐答案

在进一步检查中,我发现GIT命令行客户端与Visual Studio中的内置客户端之间存在差异.后者将TLS1.2用于https会话,而命令行使用TLS 1.0.

On further inspection I found a difference between the GIT command line client and the builtin cliënt in visual studio. The latter uses TLS1.2 for the https session, whereas the command line uses TLS 1.0.

当发生这种情况时,私有GITLAB服务器位于反向代理后面,该反向代理存在TLS1.2连接问题,从而导致行为异常(提取&拉动OK,不进行推送).

As it happens out private GITLAB server is situated behind a reverse proxy that has problems with TLS1.2 connections resulting in the weird behaviour (fetch & pull OK, no push).

这篇关于Git push在Visual Studio 2015中不起作用的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆