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 "%m %U%q %H" %s %b %D "%{Referer}i" "%{User-Agent}i" "%{jira.request.assession.id}r""/>
</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
The misconfiguration was :
that's it.
hope it helps.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.