Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: DEVSRVR - Valid: from Fri, GMT until Sat, GMT - Issuer: PHP, SS, SS, SRB - Fingerprint: 5f:d:d6:dd:a6:d:a5:ac:3a:4b:7c:7d:33:e:dd:23:9f (R)eject, accept (t)emporarily or accept (p)ermanently?svn: OPTIONS of 'https://SERVER_IP/svn/myproject/trunk': Server certificate verification failed: certificate issued for a different hostname, issuer is not trusted (https://SERVER_IP) If the client receives a server certificate, it needs to verify that it trusts the certificate: is the server really who it claims to be?I think SVN is trying to cache the server certificate and failing to do so.
If Open SSL is unable to automatically trust the CA, or if some other problem occurs (such as an expired certificate or hostname mismatch), the Subversion command-line client will ask you whether you want to trust the server certificate anyway.
When using SVN to connect secure server, the server needs to send its certificate to the client for verification.
In some cases, the certificate sent by the server is not a trusted certificate, the client may choose to trust the certificate if the server is target server for sure.
But users may get "Error validating server certificate for 'https://...'" the next time when they try to connect to the same secure server even if they specified "p" the first time when they are prompted to accept the server certificate.
Error validating server certificate for 'https://example.com': - The certificate is not issued by a trusted authority.
Firt of all to thank you for this great and useful app.