After setting up Nginx to proxy to JIRA, none of my assets (CSS, JS or images) load

Martin Sweeny1

This question is in reference to Atlassian Documentation: Integrating JIRA with Nginx

I set up the Nginx proxy as described here.

When I go to JIRA, anything at <base url>/s/ seems not to load. Most of the application's assets like CSS, JS and images seem to be found at this path.

Accessing JIRA directly, bypassing the proxy, works fine.

If I follow the URL of the assets (for example using the Networks tab of Chrome's debugging tools), I see a JIRA 404 page, rather than nginx.

My configurations:

<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"
                   proxyName="<domain>"
                   proxyPort="80"/>

server {
    listen <domain>:80;
    server_name <domain>;
    location /jira {
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass http://localhost:8080/jira/;
        client_max_body_size 10M;
    }
}

Where <domain> is the domain at which I wish to access JIRA

Martin Sweeny1

I checked out my access logs for JIRA, located at /opt/atlassian/jira/logs/ which showed me requests similar to "GET /jira//s/d41d8cd98f00b204e9800998ecf8427e-CDN/[...]" - there is an extra slash by /jira//

So double-checking my nginx and JIRA config shows the only trailing slash - in the nginx config.

Changing proxy_pass http://localhost:8080/jira/ to proxy_pass http://localhost:8080/jira fixed it for me.