Oddly enough, there was literally a similar problem a day ago. Anyway, I could be wrong, but the obvious security level for SVN in 1.8.8 is tougher than previous versions. Which certificates that you forced svn to accept can no longer be "acceptable" by the new standards. I was wrong, but it does not matter.
If you look at the error you provided, you will see:
The host name of the certificate does not match.
This is an SSL error that svn will not ignore, it means that you are connecting to a different host name than what you indicated. The fact is that https://192.168.100.59:443 can refer to the same URL as your repository server, for example: https://foobar.com:443 SSL handshaking will not be performed if host names do not match.
This issue persists for any case where your hostname of the repository URL does not match the SVN server certificate response.
I assume that you are using a self-signed certificate through the VisualSVN certificate creation tool. To resolve, renew the new certificate and verify that the host name matches the name of your real host . This should solve your problems.
Please note: you will still receive this first dialog box warning you that you are using a certificate that is not verified / valid, but you should not get this second dialog box. In addition, make sure that the client and server versions of SVN are the same and that different versions of SVN are causing great chaos.
Edit:
Sorry, I read the error back, your certificate host name is apparently 571458-tools1 when it should be 192.168.100.59 if you want to access it. Follow the same certificate regeneration procedures, but use the host name 192.168.100.59 instead of 571458-tools1 .
Please note that this will enable SSL / TLS only when directly using the internal IP address.
initramfs
source share