title: Subversion Server SSL certificate verification failed: and other reason(s)
body: <p>I had a SVN system up and working just fine, and after a recent upgrade suddenly stopped working.  My setup:</p>
  
  <ul>
  <li><p>I have a repository hosted on a Windows 2008 server using VisualSVN Server 2.7.4.  The server offers me the ability to generate self-signed certificates at will, entering my own hostname or other data as desired.</p></li>
  <li><p>I am using Eclipse (Kepler) for java coding on both the hosted machine and my own MacBookPro running Mac OS X 10.9.1 (Mavericks).  I have the subclipse add-on to Eclipse which requires subversion with java HL.</p></li>
  <li><p>I have installed macports and the latest subversion/javahl packages requested by subclipse.  The Eclipse/subversion interface seems to be working fine, but there are command-line subversion errors which Eclipse isn't navigating well.  Solving the command-line errors is the main issue.</p></li>
  <li><p>I previously had the following versions installed via macports, and things seemed to be working fine:</p>
  
  <p>subversion @1.8.5_1+universal<br>
  subversion-javahlbindings @1.8.5_0+no_bdb+universal</p></li>
  <li><p>As part of installing/troubleshooting something unrelated, I upgraded all my macports, which installed the following new versions:</p>
  
  <p>subversion @1.8.8_0+universal<br>
  subversion-javahlbindings @1.8.8_0+no_bdb+universal</p></li>
  <li><p>After the upgrade, svn via eclipse on my mac fails.  I can force it via the commandline by temporarily accepting a certificate.  It still works completely fine on the Windows 2008 server machine.</p></li>
  </ul>
  
  <p>The first time following a certificate change I get the option to accept permanently, but after doing this, it fails and falls back to a second "temporary" dialogue.  </p>
  
  <blockquote>
  <pre><code>$ svn update
  Updating '.':
  Error validating server certificate for 'https://192.168.100.59:443':
   - The certificate is not issued by a trusted authority. Use the
     fingerprint to validate the certificate manually!
   - The certificate hostname does not match.
  Certificate information:
   - Hostname: 571458-tools1
   - Valid: from Feb 28 23:57:35 2014 GMT until Feb 26 23:57:35 2024 GMT
   - Issuer: 
   - Fingerprint: 55:3E:55:FD:4D:40:A4:1E:8A:1E:27:71:DD:D4:ED:8B:A3:9A:1D:EC
  (R)eject, accept (t)emporarily or accept (p)ermanently? p
  Error validating server certificate for 'https://192.168.100.59:443':
   - The certificate has an unknown error.
  Certificate information:
   - Hostname: 571458-tools1
   - Valid: from Feb 28 23:57:35 2014 GMT until Feb 26 23:57:35 2024 GMT
   - Issuer: 
   - Fingerprint: 55:3E:55:FD:4D:40:A4:1E:8A:1E:27:71:DD:D4:ED:8B:A3:9A:1D:EC
  (R)eject or accept (t)emporarily? t
  (credentials dialogue)
  At revision 46.
  </code></pre>
  </blockquote>
  
  <ul>
  <li>Following this, future attempts still result in the error and requirement to temporarily accept:</li>
  </ul>
  
  <blockquote>
  <pre><code>$ svn update
  Updating '.':
  Error validating server certificate for 'https://192.168.100.59:443':
   - The certificate hostname does not match.
   - The certificate has an unknown error.
  Certificate information:
   - Hostname: 571458-tools1
   - Valid: from Feb 28 23:57:35 2014 GMT until Feb 26 23:57:35 2024 GMT
   - Issuer: 
   - Fingerprint: 55:3E:55:FD:4D:40:A4:1E:8A:1E:27:71:DD:D4:ED:8B:A3:9A:1D:EC
  (R)eject or accept (t)emporarily? t
  At revision 46.
  </code></pre>
  </blockquote>
  
  <p>Multiple web searches, including this site and others, have pointed to the authentication files in ~/.subversion as potentially the problem, but all the proposed solutions (deleting, changing ownership and permissions, etc.) have failed to solve the problem.</p>
  
  <p>Specific questions:
  1. I can't figure out how to revert to the previous subversion (1.8.5) in macports to see if there was a bug in the 1.8.8 version I updated to.
  2. Assuming there's no bug in 1.8.8, is there anything else I can do to potentially troubleshoot this and get my certificates permanently accepted?</p>
  
  <p>EDIT:
  - I've been able to get rid of the "hostname" error by changing my self-signed certificate hostname to the numeric IP.  However, all other symptoms remain, including the mysterious "The certificate has an unknown error."
  - I'm convinced (though comments indicate otherwise) that the 1.8.8 upgrade broke something on Mac OS X and am very interested in rolling back versions to troubleshoot further. But I suppose that's a new question...</p>