Jira Service Desk URL issue

Rahul Joshi

Hi friends I am using Jira SD as belows but with few customizations-

Client Browser -> HTTPS -> Apache Proxy -> HTTP -> Tomcat (JIRA)

#Configured JiraSD URL for public as https://support.xyz.abc

#Using *.xyz.abc wild certificate on gateway (not on JiraSD host)

#Installed/configured JiraSD http://192.168.5.33:8080

#configured base URL in server.xml as belows-

<Service name="Catalina">

<Connector port="8080"

maxThreads="150"
minSpareThreads="25"
connectionTimeout="20000"

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

#apache conf is as below-

<VirtualHost *:80>
ServerName support.xyz.abc

CustomLog /data/web/log/support.access.log combined
ErrorLog /data/web/log/support.error_log
LogLevel warn

ProxyPreserveHost On
ProxyRequests Off
ProxyPass / http://192.168.5.33:8080/
ProxyPassReverse / http://192.168.5.33:8080/

<VirtualHost >

 

still getting "We have detected potential problem with Jira's dashboard"

 

 

Andy Heinzer

I see two possible problems:

1. I'm concerned that the apache configuration seems to be using a virtualhost on port 80.  If SSL is being terminated on the reverse proxy, I would expect this to use the 443 port which is default to https connections.   
2. The /conf/server.xml is missing the proxyName, proxyPort, and scheme parameters.  These are expected when you're using a reverse proxy.  I'd recommend using the Integrating Jira with Apache SSL guide for more details.   I would expect it to look more like this:

 

<Connector port="8080"

maxThreads="150"
minSpareThreads="25"
connectionTimeout="20000"

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

proxyName="support.xyz.abc"
proxyPort="443"
scheme="https"/>

After you update this server.xml with those, you will need to restart Jira for those setting changes to take effect.  I'd be interested to see if this perhaps resolves the warning you are seeing when visiting the site that way.