But as stated below, I don't know a lot about git) (edit: no response could be because my local repo was already up-to-date, so nothing to do. Just runs for a second then returns to the command prompt. Tried this - no message or any output at all. In order of how helpful I think they may be.Īs I stated, I can ssh into the server without issue, and without entering the passphrase.Ĭan you try running that git command git -c diff.mnemonicprefix=false -c core.quotepath=false -no-optional-locks fetch -no-tags SiteGround directly from your command line? It should giver that same message about pressing y to trust this host. Take a look at these following links, you're not the only one who's faced this problem. WinSSH-Pageant hasn't even been engaged yet according to your log paste. I try not to point fingers but this isn't exactly an issue with winssh-pageant, all it does is proxy the key requests to the proper location, which only happens after you've confirmed you trust the ssh server. Or try connecting to your git repository directly from the PuTTY UI, you don't need to actually log in, just have putty open a window asking you to confirm the key is valid. Once the key has been cached this shouldn't be an issue for you any further. It appears to be hanging because the server's host key has never been cached (AKA sourcetree thinks you've never interacted with that server using ssh before).Ĭan you try running that git command git -c diff.mnemonicprefix=false -c core.quotepath=false -no-optional-locks fetch -no-tags SiteGround directly from your command line? It should giver that same message about pressing y to trust this host. Hence why I am trying winssh-pageant, but can't get it to work. SourceTree was working before, using its (or git's) ssh client, but of course it always asks for the passphrase after logging out or restarting. I tried importing the SSH key and saving it as a ppk and setting that in SourceTree options, but still no go. So it does not look like SourceTree/git is able to communicate with the server at all. I also found that if I refresh the remote branch list in the Pull dialog, the list is emptied, and I can't initiate a pull at all.
So it seems to be waiting for a response, but I can't respond from within SourceTree.
If you trust this host, enter "y" to add the key to
The server's ssh-ed25519 key fingerprint is: That the server is the computer you think it is. Git -c diff.mnemonicprefix=false -c core.quotepath=false -no-optional-locks fetch -no-tags SiteGround
0 kommentar(er)
