Arg… this is one of those posts that hopefully will save someone some pain in the future, I just spent the last 30 minutes beating my head against a wall.

I’m working on a windows 2003 server which uses VisualSVN as the management piece to the SVN repository.  So I wanted to add a post-commit hook to update the development version of the code whenever a commit was made.

Easy stuff right? That’s what I thought… added the post-commit.bat file to the hooks directory under the repository.  So far so good, made a code change… commited … and got this:


Error validating server certificate for 'https://svn.funkyproject.com:8443':
- 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: funkyhostname
- Valid: from Wed, 16 Apr 2008 05:54:20 GMT until Sat, 14 Apr 2018 05:54:20 GMT
- Issuer: funkyhostname
- Fingerprint: 05:cb:80:81:f3:4e:c8:ba:fd:b4:13:d2:c6:dd:95:69:ed:f8:77:0b
(R)eject, accept (t)emporarily or accept (p)ermanently? svn: PROPFIND request failed on '/svn/projecturfapp/trunk'
svn: PROPFIND of '/svn/projecturfapp/trunk': Server certificate verification failed: certificate issued for a different hostname, issuer is not trusted (https://svn.funkyproject.com:8443)


So after doing some googling I finally found this blog post from Dan Hounshell. His thoughts are exactly what the issue was the Local System User didn’t have the certificates accepted, changed it to a user account with appropriate access restrictions and problem solved.

Living in a multi-os world is a PITA sometimes. Negotiating the idiosyncrasies of one operating system versus the other, where things are super easy in one and with just the right bit of salt doable in the other. Finding that pinch of salt is the agonizing part.

Posted by CobyR on Sunday, November 2nd, 2008 at 11:21 pm.