I've installed Confluence 5.6.1 and JIRA 6.3.4 on the same linux server (different tomcat instances) and this went fine.
I was now trying to configure JIRA over SSL, using SSLPort=8483 and JiraPort=8080 but whenever I try to access http://jira.url.com:8080 instead of redirecting to https://jira.url.com:8483 it redirects to https://confluence.url.com:8443 (???)
Can anyone please advise what am I doing wrong?
<Connector port="8483" protocol="org.apache.coyote.http11.Http11Protocol" maxHttpHeaderSize="8192" SSLEnabled="true" maxThreads="150" minSpareThreads="25" enableLookups="false" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" useBodyEncodingForURI="true" keystoreFile="/home/jira/.keystore" keystorePass="(removed!)" keyAlias="tomcat"/>
<security-constraint> <web-resource-collection> <web-resource-name>all-except-attachments</web-resource-name> <url-pattern>*.jsp</url-pattern> <url-pattern>*.jspa</url-pattern> <url-pattern>/browse/*</url-pattern> </web-resource-collection> <user-data-constraint> <transport-guarantee>CONFIDENTIAL</transport-guarantee> </user-data-constraint> </security-constraint> </web-app>
Thanks in advance.
Do yourself a favour and terminate SSL at an nginx or apache reverse proxy (nginx is better)
That way, at upgrade time, you don't have to muck with SSL at all
If you set JIRA and Confluence to listen on different ports on the localhost there is no way to bypass the proxy.
This is a good starting point http://www.servicerocket.com/blog/2014/07/3-steps-in-set-up-nginx-as-proxy-server-for-atlassian-jira/
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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