FYI, downgrading TortoiseSVN from 1.5.5. to 1.4.8 solved the
"connection closed unexpectedly" error for me.
On Tue, Nov 18, 2008 at 10:25 AM, Stephen Dewey
<stepheneliotdewey_at_gmail.com> wrote:
> On Tue, Nov 18, 2008 at 3:53 AM, Kurt Pruenner <leak_at_gmx.at> wrote:
>> Stephen Dewey wrote:
>>> If I use svn+ssh with an SSH account (after running svnserve -t), I
>>> get the error "connection closed unexpectedly."
>>
>> Why exactly are you running "svnserve -t" in the first place?
>>
>> If you have an ssh daemon running on your server and subversion is
>> installed and in your user's path that should be enough to get an
>> svn+ssh connection up and running, no configuration neccessary.
>>
> ...
>>
>> More information about running svnserve can be found here:
>> http://svnbook.red-bean.com/en/1.5/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.invoking.tunnel
>>
>
> Ok - you are right, I didn't need to invoke svnserve -t.
> Unfortunately, even after going through and checking everything the
> manual mentioned (including file permissions - I have now recreated
> the repository so it is owned by my ssh user), I am still getting the
> "connection closed unexpectedly" error. I do not have problems logging
> in with this user using PuTTY, and once I have logged in with PuTTY, I
> can easily check out a copy of the repository from the same server.
> But using TortoiseSVN, I am unable to do the same thing via svn+ssh.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-11-18 17:01:55 CET