Hi, we are trying to implement a JIRA+Fisheye system. I had both working together fine on our local network, but for publishing to the internet at large for working with developers outside our LAN it seemed best to allow https only.
So... I was able to setup both to use a self-generated certificate with my server's computer name on the certificate, using the information at http://confluence.atlassian.com/display/JIRA/Running+JIRA+over+SSL+or+HTTPS and http://confluence.atlassian.com/display/FISHEYE/FishEye+Quick+Start+Guide and that all worked, the two were integrated great.
But when I switched the certificates to the internet hostname I want to use and tried to access through the DNS domain address, Fisheye stopped accepting logins and started giving a java error message in red with version information CR2.7.11 FE2.7.11 (20120227023831 2012-02-27):
I tried changing Fisheye's crowd server target from http\://computername\:8080 to "https\://domainname\:httpsportnumber no dice, that made it worse, any suggestions?
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
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