Apache SSL terminiation with mod_proxy after Update Jira 4.4.0 to 4.4.3

[Beat Schnyder]

Hi all

I used to run the reverse proxy configuration with SSL termination on the apache proxy as described on http://confluence.atlassian.com/display/JIRA044/Integrating+JIRA+with+Apache#IntegratingJIRAwithApache-TerminatinganSSLconnectionathttpd . After upgrade to 4.4.3 I ran into problems:
- http://192.168.1.50:8080/jira works
- https://intranet.company.com/jira times out
- https://intranet.company.com/jira/secure/Dashboard.jspa tells me, that "We've detected a potential problem with JIRA's Dashboard configuration that your administrator can correct".
The first problem it found, that it expected the URL scheeme http, but found https. I could correct that by adding a line scheme="https" into the connector block of server.xml. Now I am getting a second messages (same place), which says:
"JIRA is reporting that it is running on the port '80', which does not match the hostname used to run these diagnostics, '443'. This is known to cause JIRA to construct URLs using the incorrect port, which will result in errors in the dashboard, among other issues. ".
Has anybody got simillar problems, or even a solution? Another paramater in the connector?

Thanks for any help
Beat

Here my configurations:

server.xml

----

<?xml version="1.0" encoding="utf-8"?>

<Server port="8005" shutdown="SHUTDOWN">

<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on"/>
<Listener className="org.apache.catalina.core.JasperListener"/>
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"/>
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"/>

<Service name="Catalina">
<Connector port="8080"

maxThreads="150"
minSpareThreads="25"
maxSpareThreads="75"
connectionTimeout="20000"
scheme="https"

enableLookups="false"
maxHttpHeaderSize="8192"
protocol="HTTP/1.1"
useBodyEncodingForURI="true"
redirectPort="8443"
acceptCount="100"
disableUploadTimeout="true"/>

<Engine name="Catalina" defaultHost="localhost">
<Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true">

<Context path="/jira" docBase="${catalina.home}/atlassian-jira" reloadable="false" useHttpOnly="true">

<Resource name="UserTransaction" auth="Container" type="javax.transaction.UserTransaction"
factory="org.objectweb.jotm.UserTransactionFactory" jotm.timeout="60"/>
<Manager pathname=""/>
</Context>

</Host>

<Valve className="org.apache.catalina.valves.AccessLogValve" resolveHosts="false"
pattern="%a %{jira.request.id}r %{jira.request.username}r %t &quot;%m %U%q %H&quot; %s %b %D &quot;%{Referer}i&quot; &quot;%{User-Agent}i&quot; &quot;%{jira.request.assession.id}r&quot;"/>

</Engine>
</Service>
</Server>
---

Apache config (inside VirtualHost):

---

<Proxy *>
Order deny,allow
Allow from all
</Proxy>

ProxyRequests Off
ProxyPreserveHost On
ProxyPass /jira http://192.168.1.50:8080/jira<br< a=""> /> ProxyPassReverse /jira http://192.168.1.50:8080/jira<br< a=""> />---

[Beat Schnyder · Accepted solution]

After contacting support without helpful result I finally found the answer myself.

To make sure Jira knows where to redirect I had to use the following directives in server.xml:

scheme="https"
proxyName="intranet.company.com"
proxyPort="443"

as it was suggested on http://confluence.atlassian.com/display/JIRA044/Integrating+JIRA+with+Apache#IntegratingJIRAwithApache-TerminatinganSSLconnectionathttpd for the case of an old apache installation. Hope anybody finds that useful.

Beat