Issue Collector does not load…

[Vicky Stamatopoulou]

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.

[Hieu Le Trung]

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

[Hieu Le Trung]

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

[Vicky Stamatopoulou]

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

[EddieW]

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.