svn: E120171: Error running context: An error occurred during SSL communication

[Graham Leggett]

Hi all,

I am trying to use the svn client to check out code from a server that expects a client certificate. The client certificate is correctly installed in the windows personal certificate store.

When I use svn checkout I get the following:

minfrin@PISTACHIO C:\Users\minfrin\src\xxx>svn checkout https://sitename/svn/xxx/trunk xxx

svn: E170013: Unable to connect to a repository at URL 'https://sitename/svn/xxx/trunk'

svn: E120171: Error running context: An error occurred during SSL communication

Is there a way to get confirmation that svn as shipped with tortoisesvn is using the windows crypto API and not openssl or something else?

Is there a way to get svn to return an error message instead of "An error occurred"?

tcpdump shows that a TLS1.3 connection is successfully established, application data is then sent from svn client to the server, but the svn client then sends a tcp fin and disconnects without waiting for a reply.

The server logs the following:

[Fri Jun 13 12:41:36.218362 2025] [ssl:info] [pid 3248:tid 3258] [client x.x.x.x:55424] AH01998: Connection closed to child 5 with abortive shutdown (server sitename:443)

Has anyone got an end to end guide to get svn to use the native windows crypto API and have client certificates work as per the defaults?

Regards,

Graham

--

[Stefan]

You should ask such questions best on the svn users list, because these things need to be implemented in the svn library, not TSVN.

[Graham Leggett]

On 14 Jun 2025, at 08:02, Stefan via TortoiseSVN <torto...@googlegroups.com> wrote:

> You should ask such questions best on the svn users list, because these things need to be implemented in the svn library, not TSVN.

Unfortunately the svn users list is unlikely to be able to tell me what build options were used to create tortoisesvn.

Can anyone confirm how to make 100% sure that the windows crypto API is being used? Tortoisesvn places config files in custom places, so I'm currently guessing and guessing incorrectly.

Regards,
Graham
--