Issue Collector does not load…

Hello,

we have defined an issue collector for a project, integrated it to our website, and this had worked fine.

We have now changed the way we call our Jira, from http://ourjirasite:8080 to http://ourjirasite/jira and can access it correctly to work with.

But… now our issue collectors won't work. We deleted the old one (because it still had our http://ourjirasite:8080 in it), and created new collectors however when we call them to provide feedback the white window comes, and the progress bar indicating loading process never goes away.

What can we do to solve this?

Browser: Safari 5.1.7, Chrome 23.0.1271.91

Chrome shows following error: Refused to display document because display forbidden by X-Frame-Options.

Best regards and thanks in advance.

4 answers

0 votes
Eddie Webb Community Champion Dec 01, 2012

DId you update the settings in JIRA admin UI for the new URL, and also (i assume using a proxy) update the underlying tomcat/jetty config for the reverse proxy URL?

https://confluence.atlassian.com/display/DOC/Using+Apache+with+mod_proxy

Sounds like that may be the issue.

Thank you Eddie for your reply.

I have edited the BaseURL already and updated the scripts of the collector pages. Using Jira and the dashboards work just fine.

It is only the issue collector page which fails to load the template for a user to fill and send us a bug report.

Jira's server.xml connector already contains… the required lines (scheme="https"

proxyName="ourjirasite" proxyPort="443" - whereby ourjirasite is the URL to our site)

We have not edited the httpd.conf yet, our Jira is installed on a Mountain Lion Server.

We created the proxy by adding a webapp plist for Jira under /Library/Server/Web/Config/apache2/webapps

Maybe it is important to say, that there are various web services running on that web server:

a wiki running directly on http://ourjirasite

jira on https://ourjirasite/jira

confluence on https://ourjirasite/confluence

etc..

I will check if editing the http daemon's config solves my problem.

Thanks again and best regards, Vicky

I got the same issue here, maybe the apache proxy cause this. Any suggestion how to fix it?

I got the same issue here, maybe the apache proxy cause this. Any suggestion how to fix it?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,781 views 11 18
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot