I'm moving my company's code repository from SVN to Git. I've set up Stash 3.3.1 behind a load balancer that's serving a self-signed cert. No matter what I do, I cannot get Sourcetree 22.214.171.124 on Windows to accept the cert. The failure I get is as follows:
"The underlying connection was closed: Could not establish trust relationship for SSL/TLS secure channel."
I've tried putting in GIT_SSL_NO_VERIFY as a system variable and inside the .gitconfig of GitBash: no luck on either. I've tried checking the Disable SSL certificate validation under Tools --> Options. No luck there, either. Also, I do not encounter this problem if I go to a straight to http: it's only happening with https connections.
I've also tried following the exceptionally unclear instructions here: https://confluence.atlassian.com/display/SOURCETREEKB/Resolving+SSL+Self-Signed+Certificate+Errors#ResolvingSSLSelf-SignedCertificateErrors-Windows
Someone has to have figured out how to do this, but both Google and Atlassian Answers have come up shy for me, or I'm overlooking the answer.
Any help would be appreciated.
-- Mike Beebe
After MUCH struggling, my team finally arrived at the answer:
This answer assumes you are using a stand-alone (non-domain) Windows 7 computer and are trying to use Sourcetree with Stash on a HTTPS address and are receiving the SSL/TLS error.
You need the following:
Copy both certs to the local Windows 7 box.
Double-click on the SERVER cert. Follow the instructions and have the wizard place the cert in the where ever it wants.
Follow the instructions for importing the DOMAIN CA CERT here: http://technet.microsoft.com/en-us/library/cc754841.aspx?ppud=4 ; you want "Adding certificates to the Trusted Root Certification Authorities store for a local computer" (third topic down). Make sure you select your DOMAIN CA CERT when importing.
From there, you should be able to access Stash via Sourcetree. Or at least we were.
This was driving me nuts, but I finally found a setting to disable cert checks to allow a self signed cert 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>
Hello, is there no other way to use a Bitbucket self-signed cert with Sourcetree than to get an 'official' AD domain cert? We are evaluating both Bitbucket and Sourcetree and it seems a bit excessive to not provide some way to accept the self-signed cert during an eval.
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event