Sourcetree cannot connect to stash - Could not establish trust relationship error.

[stefgosselin]

I get the following error when I try to connect sourcetree to the stash server at workplace.

I am already configured for bitbucket and github projects, except stash has ( I am guessing here ) an unsigned certificate that seems to be causing problems.

I have tried to resolve this in a few ways. I first believed the solution would be like 1. exporting the stash website certificate from firefox and 2. converting it to PEM and 3. adding this line to .git:

[http]
    sslCAInfo=C:/Users/Stephane/Documents/dev/ssh-key-sourcetree/stef-agdev.pem

... But this had no effect, same pop-up indicating a trust relationship error. Would anybody have an idea on how I can solve this?

Thanks.

(Screenshot of error below)

[chadclan]

This was driving me nuts, but I finally found the setting in the SourceTree.exe.config file

<applicationSettings>
    <SourceTree.Properties.Settings>
        <setting name="SourceTreeHomeWebSite" serializeAs="String">
            <value>https://www.sourcetreeapp.com/</value>
        </setting>
        <setting name="ReleaseNotesRelativeUrl" serializeAs="String">
            <value>update/WindowsReleaseNotes.html</value>
        </setting>

************* Set the value to true :)
        <setting name="AllowUncertifiedSSLRequests" serializeAs="String">
            <value>True</value>
        </setting>

*************

        <setting name="IsPortable" serializeAs="String">
            <value>False</value>
        </setting>
    </SourceTree.Properties.Settings>
</applicationSettings>

[Chris Gruszka]

I tried to resolve by appending our self-signed certificate to C:/Users/$USERNAME/AppData/Local/Atlassian/SourceTree/git_local/bin/curl-ca-bundle.crt

I got past "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel" error by having IE install the self-signed certificate to the Trusted Root Certification Authorities store.

I still have the "fatal: unable to access 'https://xxxx@xxxxx.com/scm/xxxx/xxxx.git/' ..." error