On Mar 27, 12:05 am, vfclists <vfcli...@googlemail.com> wrote:
> On Mar 26, 5:38 pm, Konstantin Khomoutov <khomou...@gmail.com> wrote:
> > On Mar 22, 4:57 pm, vfclists <vfcli...@googlemail.com> wrote:
> > > > > I keep getting
> > > > > Fatal: The remote end hung up unexpectedly
> > > > > and would like to know if there is a way to get git to give more
> > > > > detail on what is going run, like some verbosity level both on the
> > > > > server as well as locally,
> > [...]
> > > My system consists of msysgit and TortoiseGit.
> > > I setup the key using msysgit's ssh-keygen and Tortoise is able to
> > > work with it fine.
> > > I am not using the putty/plink system with msysgit.
> > [...]
> > All output seems OK to me so I don't really know what to do next as I
> > use putty suite myself.
> > One thing which could probably shed some light on your issue is to
> > enable "git tracing" before trying the offending command; try
> > something like this:
> > C:\repo> set GIT_TRACE=1
> > C:\repo> git remote show origin
> > And see what it prints.
> When I try you suggestion, a message suggesting it is using plink to
> connect, yet the ssh command works fine.
> When I try to generate a key it also complains that the id_rsa file
> already exists. It looks like although it was through Git I set up the
> ssh key, it is expecting the file to be converted for use with plink
> before it works.
> I think I will create a putty connection for the username/server and
> get the key converted and stored in it. That might work.

Creating a putty session with for the git user on the server, saving
the user name and adding the ppk to it solved the problem. It looks
like TortoiseGit uses the id_rsa key, where as msysGit doesn't, as it
probably expects a putty session with a username and saved .ppk key to
already exist for use by plink.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to