Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira is very Slow while using reverse-proxy (nginx) with SSL

M Amine
Community Champion
June 27, 2018

Hi,

We are setting up Jira (latest server version) behind a reverse-proxy (nginx). Both of them are installed in the same machine/server. 

First, we set the reverse-proxy on port 80 (http) and everything was working fine. But after setting the reverse-proxy on port 443 (https with a self signed certificate) we have been experiencing a very high latency. Jira has become unusable. 

We activated profiling logs (http, sql ...etc) on Jira and activated also logs ($request_time  $upstream_response_time  $pipe) on nginx. We noticed that the issue is not coming from nginx. It is Jira that is taking so long to server pages. 

We tried the solution described here 'https://confluence.atlassian.com/jirakb/jira-is-slow-due-to-high-latency-connections-while-using-reverse-proxy-181538995.html' but with no success.

<Engine name="Catalina" defaultHost="localhost">
<Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true">
<Context path="" 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=""/>
<JarScanner scanManifest="false"/>
<Valve className="org.apache.catalina.authenticator.FormAuthenticator" securePagesWithPragma="false" />
</Context>
</Host>
<Valve className="org.apache.catalina.valves.AccessLogValve"
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>

We also tried the solution described here 'https://community.atlassian.com/t5/Jira-questions/pragma-No-cache/qaq-p/333895' but also with no success. 

any help please? what are we doing wrong?

thank you 

2 answers

1 accepted

0 votes
Answer accepted
M Amine
Community Champion
September 17, 2018

The misconfiguration was :

  • in the Nginx Side => Had to reset everything and start from scratch
  • in AWS => 
    • Removed everything from /etc/hosts
    • Reset SG/NACL and rebuild them again properly

that's it.

hope it helps.

0 votes
Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 28, 2018

Hey Mohammed,

Do you mind pasting the connector portion of your server.xml file for inspection? If it's handy, I'd also like to take a look at your nginx configuration (at least the server block for Jira if nothing else).

Thanks,
Daniel

M Amine
Community Champion
July 4, 2018

Hi @Daniel Eads

Sorry for my late reply. 

Found the issue. Is what about a misconfiguration in Nginx. Managed to fix that and now everything is fine. 

 

thank you vm,

 

MKA

Craig Castle-Mead
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.
July 4, 2018

Hey @M Amine

Wondering if you're able to share the misconfiguration in Jira - it might be helpful in the future if anyone else has a similar issue

CCM

M Amine
Community Champion
July 5, 2018

Hey @Craig Castle-Mead,

Actually the misconfiguration was in the Nginx side + AWS (NACL, SG and EC2 /etc/hotsts). 

Ok I will describe the misconfiguration in a later post. 

MKA

Shaun September 13, 2018

Could you please post solution? We are seeing the same issue. Thanks.

Suggest an answer

Log in or Sign up to answer