Jira behind Apache Proxy on Plesk with Lets encrypt certificate

[Sebastian Schabbach]

Hi all,

I have got a fixed environment and just wan't to make jira (which is running on port 8080) to be accessed using port 80 and an context path. I worked through https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html and the key facts are as follows:

• If I proxy to https, I got an 500 error page. Don't know what the error message is in english, but I think something indicates that the connection is broken due to an ssl issue.
• If I proxy to http, the proxy works, but jira displays an error that the proxy used the wrong port and there are some display errors in the gadgets from jira.
• I have got no certificate in jira, so jira is using the lets encrypt certificate from apache

I would like you to give me best practice hints on that szenario. What might the connector look and whats the recommendations about mixing HTTPS and local HTTP. Or how to use the certificate from the apache webserver.

Kind regards

[Andy Heinzer]

That guide is more geared to a product independent set of steps for using a proxy with most of our server products.   In this case though, I would instead recommend that you try to follow Integrating Jira with Apache using SSL instead.  Many of the steps are identical, but it does have much more a Jira specific focus.  In turn it does recommend that you have two different connectors setups within Jira; one to handle the HTTPS traffic (default 8443), and the other using HTTP that can be only accessed locally (default 8080).  This later connector will tend to help a lot with troubleshooting connection problems without always having to restart Jira to do testing.

From the steps you have taken so far, it sounds like there is a misconfiguration between the server.xml that Jira is using and the proxy itself.  Try the steps in this other KB to start. 

There is also another common environmental problem we see with Jira behind a proxy, that is that the Jira application itself is expected to be able to reach its own base URL over your network.   Sometimes that doesn't work because of network restrictions.  If that happens you tend to find that gadgets in dashboards don't work correctly, or the UPM won't be able to find plugins to install/update.   There is an additional KB that explains some of these problems and ways around them over in How to fix gadget titles showing as __MSG_gadget.