SSL handshake failed: An existing connection was forcibly closed by the remote host

[Patrick Lisser]

I faced this issue on various interactions with TortoiseSVN, namely when opening the Repo-Browser or when going to switch to from trunk to branch or vice-versa. Moreover, this error was only shown after a really long period of time (at least it felt that way).

Searching for advice on various forums didn't help (or better: were mostly misleading), so after I found the (pretty dumb) reason, I decided to post it here.

In my case it was the proxy setting (TortoiseSVN/Settings -> Network) or more precisely I once entered a proxy server in order to get access to an external repository and after that I got the above error while trying to access repositories on the intranet.
The solution, quite clearly, was just to disable the proxy server.

Hope this helps someone to solve the same issue faster than me :-)

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2863434

To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].

[Matt Hamilton]

Please be advised, we are experiencing the same symptoms that were described above. We have performed a lengthy series of tests against the different versions of TortoiseSVN to try and provide as much background as possible.

Environmental variables:
o Subversion version 1.6.4 (r38063)
o TortoiseSVN versions tested
o All 1.7.x versions have been tested

-----------------------------------------------
---- Begin Report Bug -------------------------
-----------------------------------------------
The action performed: SVN Update

Expected Outcome: An Update of the working copies from the SVN repository

Actual Outcome: An SSL Handshake error
<Sanitized Error:

Action: Path:
Error Unable to connect to a repository at URL
Error 'https://udevelop.<sanitized>.com/svn/ams-custom'
Error OPTIONS of 'https://udevelop.<sanitized>.com/svn/ams-custom': SSL handshake failed:
Error An existing connection was forcibly closed by the remote host.
Error (https://udevelop.<sanitized>.com)

>
-----------------------------------------------
---- End Report Bug ---------------------------
-----------------------------------------------

-----------------------------------------------
---- Begin Work around ------------------------
-----------------------------------------------
For versions 1.7.0 to 1.7.6 the following seems to fix the issue. (This does not work for 1.7.7)

1. Go to the SVN Repo Browser
2. Save authentication details

Once the details are saved, all other actions appear to work just fine. I noticed in the Change Logs that a similar BUG was corrected on Version 1.7.3 (Issue 155: crash when accessing a server with an invalid ssl certificate. (Stefan))

We are experiencing this issue in versions Pre and Post 1.7.3.
-----------------------------------------------
---- End Work around --------------------------
-----------------------------------------------

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2969562

[Stefan Küng]

On 07.06.2012 18:33, Matt Hamilton wrote:
> Please be advised, we are experiencing the same symptoms that were
> described above. We have performed a lengthy series of tests against
> the different versions of TortoiseSVN to try and provide as much
> background as possible.
>
> Environmental variables: o Subversion version 1.6.4 (r38063) o
> TortoiseSVN versions tested o All 1.7.x versions have been tested
>
> ----------------------------------------------- ---- Begin Report Bug
> -------------------------
> ----------------------------------------------- The action performed:
> SVN Update
>
> Expected Outcome: An Update of the working copies from the SVN
> repository
>
> Actual Outcome: An SSL Handshake error <Sanitized Error:
>
> Action: Path: Error Unable to connect to a repository at URL
> Error 'https://udevelop.<sanitized>.com/svn/ams-custom' Error
> OPTIONS of 'https://udevelop.<sanitized>.com/svn/ams-custom': SSL
> handshake failed: Error An existing connection was forcibly
> closed by the remote host. Error
> (https://udevelop.<sanitized>.com)

Now this should be your clue: the connection was closed by the *remote
host*, which means the *server* closed the connection for some reason.

Usually in such situations there's an entry in the Apache log that gives
you more information about why the connection was closed.

Your server also is very old. If you don't want to upgrade to 1.7, then
at least update it to svn 1.6.18!

Stefan

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2969572

[Matt Hamilton]

Stefan,
Thanks for the prompt response. I will forward your suggestions on to our server team.

If I am hearing you correctly though, it is your opinion that the issue is related to the old Subversion server instance not being compatible with the new TortoiseSVN?

To restate: Are you saying that Tortoise is most likely trying to authenticate with SSL that the old version of Subversion doesn't understand?

OR is the error too nondescript to even try and guess what the true error is?

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2969595

[Stefan Küng]

On 07.06.2012 20:24, Matt Hamilton wrote:
> Stefan, Thanks for the prompt response. I will forward your
> suggestions on to our server team.
>
> If I am hearing you correctly though, it is your opinion that the
> issue is related to the old Subversion server instance not being
> compatible with the new TortoiseSVN?
>
> To restate: Are you saying that Tortoise is most likely trying to
> authenticate with SSL that the old version of Subversion doesn't
> understand?

there's a good chance of that, yes: TSVN always links with the latest
version of OpenSSL. And if you recall, OpenSSL had a few cipher
algorithms deactivated by default for security reasons. TSVN always
builds with the defaults, so those weak ciphers are not available
anymore when using TSVN, but your server might still expect them.

> OR is the error too nondescript to even try and guess what the true
> error is?

To narrow down the problem, you have to check the Apache error log:
there should be an entry every time you get the error that the
connection was closed by the server. And that entry should give you more
information why that happened.

Stefan

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------

http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2969596

[Matt Hamilton]

I'm sorry for resurrecting such an old post. However, we just got our SVN server software upgraded to 1.7.9. After the upgrade we are still getting the same error. Version of Tortoise most recently tried:
TortoiseSVN 1.7.7, Build 22907 - 64 Bit , 2012/05/15 12:16:05
Subversion 1.7.5,
apr 1.4.6
apr-utils 1.3.12
neon 0.29.6
OpenSSL 1.0.1c 10 May 2012
zlib 1.2.7

At this point, I believe the issue is in-fact with our server configurations. However, I would prefer to make a very specific request to the server team for assistance. Would you be able to advise what I should have them look at? You mentioned the "Apache error log" is this the only place they should look for errors?

Thank you for your continued support.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3061568