I have Jira behind a proxy:
https -> http
It works pretty well, but there are still some bugs.
- Activity tab does not work behind proxy
- some *.js file get http instead of https (-> 404)
It sounds like you're using an Apache proxy to terminate SSL there, and then Jira just has a standard http connector. If that is the case, then I would recommend reviewing our guide on Integrating JIRA with Apache using SSL.
It is a common oversight that after you have configured the proxy, that lots of admins forget that you have to go back to Jira's Tomcat server.xml and update this in order to tell the tomcat connector that its traffic is being redirected to it.
For example, your $JIRAINSTALL/conf/server.xml should have within the connector, the parameters such as:
scheme="https" proxyName="jira.atlassian.com" proxyPort="443"
If these don't exist in the connector, then Jira's Tomcat instance is not properly aware of the existence of this proxy that is redirecting this traffic.
Also if you have to add these parameters in, you will need to save that file, and then restart Jira in order for these changes to take effect.
I hope this helps.
It may be that you haven't fully configured Jira to run over SSL.
Have you modified your web.xml to redirect HTTP to HTTPS?
Instructions can be found towards the end of this guide:
Running JIRA applications over SSL or HTTPS
If redirection to HTTPS will be used (this is recommended), edit the <
JIRA_INSTALL>/WEB-INF/web.xml file and add the following section at the end of the file, before the closing
</web-app>. In this example, all URLs except attachments are redirected from HTTP to HTTPS.
<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> <url-pattern>/issues/*</url-pattern> </web-resource-collection> <user-data-constraint> <transport-guarantee>CONFIDENTIAL</transport-guarantee> </user-data-constraint> </security-constraint>
If this isn't your issue we would need more information about how you've configured HTTPS in order to get a better idea of what configuration needs to be fixed.
no jira is running on http.
There is a Apache as a proxy which accepts https and then calls jira on http:
Allow from all
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
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