Jira Apache integration

James Saxton November 17, 2015

JIRA 6.3.3  and Apache 2.2   both on same linux server.

Apache listening on port 444 ( for now ) using SSL

JIRA SSL on port 8443.

JIRA works perfectly fine without Apache

Apache is configured using reverse proxy  ( ssl.conf )

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

ProxyRequests           Off
ProxyPreserveHost       On
ProxyPass               /jira       http://FQHN:8881/jira/
ProxyPassReverse        /jira      http://FQHN:8881/jira/

</VirtualHost>
server.xml connector

 <Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true"
           enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25"
           port="8881" protocol="HTTP/1.1" redirectPort="8443" useBodyEncodingForURI="true"
           scheme="https" proxyName="FQHN" proxyPort="444"/>

 

All javascript seems to end in a 404 through the apache webserver - so my JIRA UI is just unaligned text.

 

GET /jira/s/d41d8cd98f00b204e9800998ecf8427e-CDN/en_US-m3jqk5/6331/4/3.5.6/_/download/batch/com.atlassian.gadgets.dashboard:gadget-dashboard-resources/com.atlassian.gadgets.dashboard:gadget-dashboard-resources.js HTTP/1.1" 404 2369

156.119.247.103 - - [18/Nov/2015:00:00:45 +0000] "GET /jira/s/595e31d08792ab5c2fcdb17a5fc632cb-T/en_US-m3jqk5/6331/4/1.5/_/download/batch/com.atlassian.administration.atlassian-admin-quicksearch-jira:admin-quicksearch-webresources/com.atlassian.administration.atlassian-admin-quicksearch-jira:admin-quicksearch-webresources.js?locale=en-US HTTP/1.1" 404 2369

 

 Not sure where to look - all suggestons much appreciated.

 

JIM

 

 

1 answer

1 vote
Jonas Andersson
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 17, 2015

First off: Edit your entry and remove the URL that is lurking under the links still, not allowing people to actually see what server urls you exposed to the web.

About your problem. Use bugzilla webbrowser plugin or other html analyzing tool and look at the full requests. Copy paste the requests directly to a webbrowser and manually rewrite the URL's between the native/proxied ports (8443, 888, 444) to see where you get a 404 and where you get a 200. Make sure nothing is added to the urls that fail (i.e FQDN/jira/jira/... for instance)

This should allow you to get closer to figure out where things go wrong.

Suggest an answer

Log in or Sign up to answer