nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

When using reverse proxy, gedget in dashboard failed to display

Ryan_af89nk

Hello Team,

We plan to use Nginx reverse proxy to forward 80 port traffic to Jira's port 8080. Configuration has been done. we can access Jira via 80 of most functions. but we found certain gedget in dashboard failed to display. When investigate, we found the gadget is still requestiong to 8080 port directly, and it is not allowed in browser, while main page use 80 port.

Any solution to fix it?

Thank you!

Ryan

Accepted answers

All comments

Nic Brough -Adaptavist-

That sounds like the gadget has a bug, or has a configuration item that allows for a broken url.

Which gadget is it?

Ryan_af89nk

In my case, currently, 2 gadget of 'Time to SLA' add on, which is SLA status Pie chat, TTS - Periodic Met vs Exceeded SlA,

Anther is build in Activity stream.

I see either below error under my dashboard,

We've detected a potential problem with JIRA's Dashboard configuration. Hide Close

Dashboard Diagnostics: Mismatched URL Port

JIRA is reporting that it is running on the port '8080', which does not match the hostname used to run these diagnostics, '80'. This is known to cause JIRA to construct URLs using the incorrect port, which will result in errors in the dashboard, among other issues.

The most common cause of this is the use of a reverse-proxy HTTP server (often Apache or IIS) in front of the application server running JIRA. While this configuration is supported, some additional setup might be necessary in order to ensure that JIRA detects the correct port.

The following articles describe the issue and the steps you should take to ensure that your web server and app server are configured correctly:

If you believe this diagnosis is in error, or you have any other questions, please contact Atlassian Support.

Detailed Error

Click here to learn more

Nic Brough -Adaptavist-

Ahh, so you've not configured the proxy correctly. I am sorry, the question suggested it was just one gadget having a problem.

First, can you check the basics:

Your base url is set to the place the users will be using (i.e. the proxy front end, not Jira's 8080 based url)
The context is correct (if you are using one at all)
Jira's server.xml has the right proxyport, proxyname and scheme settings in the connector
The proxy has the matching context and proxypass settings

Ryan_af89nk

Hello Nic Brough,

Thank you for your reply,

In fact, I was following this guide https://confluence.atlassian.com/jirakb/integrating-jira-with-nginx-426115340.html to config the reverse proxy using nginx.

The base url is exactly the front URL of nginx http://sd.softtekchina.com
The context is <Context path="" docBase="${catalina.home}/atlassian-jira" reloadable="false" useHttpOnly="true">
Jira server.xml reverse proxy section is set as:

<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" scheme="http"

proxyName="sd.softtekchina.com" proxyPort="80"/>

The proxy is matched with server.xml

server {

listen 80;

server_name sd.softtekchina.com;

location / {

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://sd.softtekchina.com:8080/;

client_max_body_size 10M;

}

The rest of functions work well, only some gadget.

Thank you

Ryan

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-core

jira-core-server