Forums

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

Gadgets not working with apache front end

Jason White
Contributor
May 4, 2012

As in the directions (http://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Apache#IntegratingJIRAwithApache-Enablemodproxyandmodproxyhttp) .... I have the following set up:

This is a 'stand-alone' install:

{atlassian.home}/jira/conf/server.xml

<Context path ="/JRA" ... >

{httpd.home}/conf/httpd.conf

<VirtualHost xxx.xxx.xxx.xxx:80>
... 
ProxyPass /JRA http://localhost:8080/JRA
ProxyPassReverse /JRA http://localhost:8080
</VirtualHost>

This is on a RHEL 5 box. I'm using multiple IPs in my virtual host config (one is dedicated to JIRA .. going to add SSL later, butjust want to get the basic proxy part working first).

Everything works fine, can log in etc., but gadgets don't work. Nothing in the dashboard and get 'gadget directory failed to load' when I click to add gadget. I only have it configured to respond to a single URL and am using a dedicated IP for each vHost in apache. No 404's in apache except for favicon and /secure/useravatar?bla=blah ...

Any ideas?

2 answers

1 accepted

0 votes
Answer accepted
Jason White
Contributor
May 5, 2012

As noted above ...

ProxyRequests off
ProxyPreserveHost on

in the httpd.conf VirtualHost stanza did it.

0 votes
EddieW
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.
May 5, 2012

Not to be daft, but is it the missing context on the reverse proxy statment? (no JRA shown above)

That would make responses look to come from a different URL.

1
2
3
4
5
<VirtualHost xxx.xxx.xxx.xxx:80>
...
ProxyPass /JRA http://localhost:8080/JRA
ProxyPassReverse /JRA http://localhost:8080/JRA # <-- Added context
</VirtualHost>
Jason White
Contributor
May 5, 2012

Yes ... I had to type it in here as opposed to copy/paste. Legitimate question ... but it's something different, although similarly simple. I noted that I did *not* have:

ProxyRequests off
ProxyPreserveHost on

in my httpd.conf VirtualHost stanza ... that did it.

Sometimes, you just need a night of sleep to see the obvious. ;-)

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, state of product 2026, product teams report, developer experience, product manager survey, AI impact, product team stress, product teamwork, dev workflow insights, 1000+ PMs, product leadership research

State of Product 2026

State of Product 2026: your pulse check on product development today. We asked 1000+ real teams how they’re feeling–and they had a lot to say.

Get the report
AUG Leaders

Atlassian Community Events