-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error pushing to git remote with http #1138
Comments
Oh that's terrible, sorry for that! |
I assume a simple |
Yes, "git push" from the command line works |
Git seems to do this, not VS Code. Here's a snippet from the command line:
Is your host by any chance GitHub or BitBucket? Which command line exactly are you using? Closing as dupe of #490. Will reopen if further information reveals this to be an independent issue. |
My repo is GitLab CE
The URL with the final slash only apears in VSCode and if i put this URL in Chrome for example return ERR_TOO_MANY_REDIRECTS Why VSCode connect with the remote and add a final slash? |
Note: the error is in VSCode when I do a push or a pull in the Git feature |
Is there any way you can set up a repository in that same server and give me credentials to access it so I can try to repro? |
the same error in gitlab.com repository.
I invite you in a public repository for testing and "master" role :) |
I do this: git push origin master from command line works! |
Thanks for the repo access. There was definitely a problem with VS Code's credential helper. When running the push action, you should have seen this dialog: The dialog is not showing up in With the fix, I was able to successfully push to the GitLab repo using the credentials I configured in the GitLab website. |
This dialog is showing to me. I put the credentials and show the error |
I know my credentials. I use this repository from several project with eclipse and command line too and works with ssh and https connections. Thank for all :) |
If you use the SSH remote url, it should all work, since no password prompt will occur. If you use HTTPS, you should get the prompt. I do, I input the credentials I configured in GitLab and it works for me. Maybe it's platform specific? Which platform are you on? |
I have a development server on my domain that's running Bonobo Git Server set up to use Windows authentication. My credentials work everywhere except in VS Code. I get a similar authentication error with the trailing slash. |
The new versión of VSCode WORKS :) Thanks and go on! |
I'm using VSCode 0.10.6 (newest version) and I still have this problem. |
@TejasCMehta; Fixed the problem for me! |
@TejasCMehta |
I also arise same bug on windows8. |
I wouldn't use store for this since as per git specs it store the password unencrypted on disk https://git-scm.com/docs/git-credential-store I would use
instead with optional timeout https://git-scm.com/docs/git-credential-cache This is still just a workaround until a proper fix but it works. |
I support the cache credential helper as a workaround until we tackle this issue head on. |
I'm running into this problem too. I do not get presented with a credential dialog. |
Similar set up to BryanConradHart getting the error |
same as @jonathanfishbein1. Linux Mint 17.3 |
I am also facing the same problem |
The authentication dialog was fixed by #1796, it should start coming up on the next release. Meanwhile, I do suggest using a credential helper. |
I'm running into the same error.
I downloaded and installed the credential helper then tried both: ps. I'm using version 1.2.1 Thanks a lot for your support. |
I was having a similar problem with OSX. I turned OFF 2 - factor authentication and the problem resolved itself. |
I tried pushing to git hub but I got an error message saying couldn't connect to server . What can I do? |
To @jm-rives and others make sure to follow > Authorizing when using two-factor auth I hope it helps. |
I have configured my git remote like this:
And when i do a push show me an error:
Why Visual Studio Code add the final slash? :(
The text was updated successfully, but these errors were encountered: