It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Apache 2.4 Reverse Proxy Gadget.common.error.500

Hello everyone, 

I'm currently trying to move our Jira instance to a new server whilst also doing an upgrade. I've managed to restore our backups and the core Jira seems to be running pretty well. 

As with quite a few others i've been getting the "gadget.common.error.500" issue which causes most of our dashboards to fail quite spectacularly. 

I'm running an Apache 2.4 server which reverse proxies everything to Jira running on localhost, most jira functionality is working absolutely fine just now the gadgets. 

I've also updated the context path to /jira

<Engine name="Catalina" defaultHost="localhost">
<Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true">

<Context path="/jira" 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.valves.StuckThreadDetectionValve" threshold="120" />
</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>

 

My Apache Configuration is as follows

############
# Jira configuration
############

<Proxy *>
Require all granted
</Proxy>

ProxyRequests Off
ProxyPreserveHost On
ProxyPass /jira http://localhost:9090/jira
ProxyPassReverse /jira http://localhost:9090/jira

 

I should also add that none of this is going over SSL/TLS it's all just plain old HTTP. 

Any help would be really appreciated,

 

Many Thanks,

Chris

1 answer

1 accepted

0 votes
Answer accepted

Exactly 2 seconds after posting this  I figured out the issue. 

We haven't moved the DNS to the new server and currently the base URL (Administrative > System > Base URL) was setup for what the DNS entry is going to be. When I added a host file entry onto the server suddenly everything spring to life.

 

Check each of the diagnosis entries on this page https://confluence.atlassian.com/jirakb/fix-gadget-titles-showing-as-__msg_gadget-in-jira-server-813697086.html?_ga=2.58679466.1824182839.1571645804-1458963576.1562314245

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

314 views 1 3
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you