The issue turned out to be related to SSL certificates. I had a SSL cert fronting the server whose CN didn't match the Apache proxy that sits in front of all my Atlassian servers.
On an unrelated piece of work to fix the cert to make the "warning: this site may be blah blah blah" interstitial go away, the create branch started working.
I know that Atlassian servers are capable of complaining about some SSL certificate issues (i.e. if you have a private root CA and don't add the CA cert to the java certificate store, you can't create application links). Those errors appear in the logs.
This seems to be a more subtle failure where JIRA doesn't really like the Stash cert but also doesn't emit anything to the log to suggest to the user that this is the problem.
Hi, I seem to have the exact same issue as you do, but I don't understand what you did to fix it... the root signing certificate is properly imported in the cacerts file, application link seem to work well but I get the same warning about stash being too old even though I'm on 2.8.2.
I restored a backup in a VM and removed all the SSL and reverse proxy shenanigans, and jira and stash do happily connect, so somehow this is related to SSL, but given that I don't have any error message in the log I am a bit at a loss here... My CN on the ssl certificates all seem to be good also, etc...
ok so I did manage to fix the problem, it was caused because I had separate certificates for the subdomains I was using, but they were hosted on the same server (with the same ip address). I fixed it by using a wildcard certificate instead. See this: http://serverfault.com/questions/390657/do-i-need-a-dedicated-ip-address-per-sub-domain-for-ssl
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot