使用 vscode ssh 拉取、获取、推送、克隆时，我无法通过“git-credential-manager get”步骤

Question

My environment is that.

MyLaptop (Windows 10) <====> ServerPc (Windows 10) <====> github

When I connect ServerPc through remote control from my laptop, I can do full comment set of git.
But When I connect through ssh, pull/fetch/push/clone are not possible to perform. To more detail I did set GIT_TRACE=1 , then found out that git process is pending on run_command: git-credential-manager get I tried to look for the solution for it, But I can not.

Is anybody who has a similar problem here?

---

Updated

I still don't know the root cause. But I found out that Microsoft already knows this issue and they suggest workaround like below at here( https://code.visualstudio.com/docs/remote/ssh ).

If you clone a Git repository using SSH and your SSH key has a passphrase, VS Code's pull and sync features may hang when running remotely. Either uses an SSH key without a passphrase, clone using HTTPS, or run git push from the command line to work around the issue.

So I'll close this question now. Thank you for your advice everybody.

---

Updated

I changed the method of auth from password to sshkey-without_passphrase. Then, I followed @bk2204's guide that described in below. That work for me perfectly. Thank you for your advice everybody.

Answer 1

It's likely that what's happening here is that you have an askpass helper set in the environment (via GIT_ASKPASS , SSH_ASKPASS , or core.askpass ). Since Windows graphics are not network transparent, when you log into the server PC via SSH, you're invoking a graphical process on the server PC that you can't interact with. If this is the case, you'll need to unset those variables or settings when using SSH.

It could also be that you normally have saved credentials in the normal Windows credential store, but that isn't unlocked when you log in via SSH and the credential manager is hanging instead of handling it gracefully and prompting. If so, you could see if your SSH server has an option to unlock the credentials, or ask the purveyor of your credential manager to fix the hang.