The most common cause of this is either a network/proxy issue or an issue with your client accepting the SSL certificate. We use a valid SSL certificate signed by a legitimate Certificate Authority; however, many Subversion clients will not automatically accept chained certificates from anyone.

To solve this problem:

  1. Verify that you are using a recent version of your particular client. With TortoiseSVN in particular, having the most recent client version matters, as previous versions have had some issues with HTTPS access.
  2. If you're using Windows, reboot your system. Often, Windows itself or its applications will cache settings or otherwise hang on to problems that would go away after a reboot.
  3. Verify that your network can see ProjectLocker by placing your URL (e.g. into your browser. If this doesn't work, there is a firewall problem or network issue preventing you from accessing the system. If it does, the real issue may be the certificate.
  4. If you are having a network or proxy issue, contact your IT administrator to get the proxy settings for HTTPS (they should be the same as those in your Web browser), then consult your client's documentation for how to set up a proxy.
  5. If you are not having a netowrk or proxy issue, ask your client to accept the certificatepermanently. The command line application should present you with the option whenever you try to run a command. In TortoiseSVN, you'll need to navigate to Repo-Browser in the TortoiseSVN context menu, then put in the URL to be presented with the certificate. In SubClipse, you can go to the SVN Repository Browsing view and attempt to add the URL, and it should present you with the certificate. For other clients, refer to the client documentation to determine when and how you will be presented with the certificate.

 At this point, you should have access to the repository. If after following these steps you continue to see the PROPFIND error, open a ticket and ProjectLocker Support will take a closer look.