Unable to connect to SVN with Self-Signed Certificate

Nij4t2

Last week I upgraded SQL Toolbelt, and since then I have been unable to connect SQL Source Control to our SVN server with a self-signed certificate.

The error is: SharpSvn.SvnRepositoryIOException: Server SSL certificate verification failed: certificate issues for a different hostname, issuer is not trusted.

While I can not guarantee it, I am pretty certain that the only thing that changed was the upgrade (I can still connect from a different PC which did not have the software upgrade yet).

Any suggestions would be much appreciated!

Nij

Anu D

Thanks for your post.

Can you browse the SVN URL from the same machine?

And also do you have any firewall that can block the connection to SVN server?

If not can you reply my email with the complete error along with a screenshot?

Nij4t2

Hi Anu,

Yes - I can browse to the SVN repository from the same machine, but as you would expect the modern browsers will warn about the self-signed certificate! (I accept that self-signing on our SVN is not ideal; but it has been in place for some time).

Remember - this same repository is working fine when I access it from another computer with a slightly earlier version of ToolBelt on it... and I used to be able to access it from my current computer before I did the upgrade.

I will endeavour to send you the full error text by email,
Nij

Stefan Hoffmann

I have a similar problem here: A self-signed certificate. It's accepted by FF/IE with the usual are you sure dialog.

The error is SharpSvn.SvnRepositoryIOException: Server SSL certificate verification failed: issuer is not trusted.

Stefan Hoffmann

You need to import the self-signed certificate by using the command-line version of SVN or a GUI tool like TortoiseSVN. Accept the certificate with one of those tools, then it is also accepted by SQL Source Contorl (SharpSvn).

This should prominently stated with the error message as a reminder.

Nij4t2

Many Thanks Stefan,

It happens that the PC I do my SSMS work on is not technically the same PC where I do my development, so I had not installed Tortoise SVN on that machine. Now I have done (and connected to our SVN server and allowed the self-signed certificate) that SQL Source Control is now functioning.

Many thanks for your suggestion,
Nij