title: SourceTree and Stash: Unable to get local issuer certificate
body: <p>We have Atlassian Stash installed on a Windows 2008R2 server, and for the most part everything is working nicely. We have an SSL certificate issued by our local on-premise CA and a DNS entry set up so we can go to <code>https://stash/</code> and it works quite nicely, except in Firefox where it throws a warning (related?).</p>
  
  <p>When using Atlassian's Sourcetree we can navigate and choose a repository, but when we try to clone it we get the following error:</p>
  
  <blockquote>
    <p>fatal: unable to access <code>https://user@url/scm/etc/etc.git</code>: SSL
    certificate problem: unable to get local issuer certificate</p>
  </blockquote>
  
  <p>I get the same error if I try if from the git bash as well. Based on this error, I've tried <a href="http://blogs.msdn.com/b/phkelley/archive/2014/01/20/adding-a-corporate-or-self-signed-certificate-authority-to-git-exe-s-store.aspx" rel="noreferrer">following the instructions</a> on adding the SSL certificate to the Git as <a href="https://confluence.atlassian.com/display/SOURCETREEKB/Resolving+SSL+Self-Signed+Certificate+Errors" rel="noreferrer">also found on their website</a>, including what is in the comments, to no avail. I have exported the cert through Firefox and through the MMC certificate snap-in, gotten the same results and put it in its own file, combined with the curl file, and no matter what keep getting this error. I have yet to try getting it to work with SSH keys yet since I was hoping to make this easier for my team.</p>
  
  <p>I also tried using <a href="https://answers.atlassian.com/questions/260358/clone-failes-with-unable-to-access-url-unable-to-get-local-issuer-certificate" rel="noreferrer">ssh myserver</a> and accepting the connection, and I entered my password and restarted; still the same error.</p>
  
  <p>I do not want to simply <a href="https://stackoverflow.com/a/4454754/792032">ignore certificate validation</a> either, since that seems a bit pointless, then.</p>
  
  <p>How can I get this working with our CA-issued cert?</p>