Hello Atlassian Community!
We're currently having a few issues with our locally installed JIRA implementation.
A few things to note with our set up:
Please let me know if more information is needed, and thank you for your time as always!
I would recommend starting with the guide How to bypass a Proxy and SSL to test network connectivity. I suggest this because it is possible that your proxy could be blocking certain traffic or that Jira is not yet properly configured to use this proxy. By circumventing this proxy it helps us to understand if the problem is caused by the proxy, or is completely unrelated to this.
If this problem is not repeatable when bypassing the proxy, then this is probably a good indication that there is a configuration problem here. I would recommend reviewing the Proxying Atlassian server applications with Apache HTTP Server (mod_proxy_http) guide as this explains how Jira is expecting to be configured and how the apache proxy should be setup as well.
The most common step I see users omit is on Step A, part 3: Configure the Connector directive. Typically if you forget to configure Jira's server.xml to contain the parameters:
proxyName="<subdomain>.<domain>.com" proxyPort="80" scheme="http"
Then the Jira application is not aware its traffic is being routed through the proxy and can frequently cause problems like this.
Try this and let me know the results.
It looks like it had something to do with the vhost.conf file. I ended up copying the syntax from the known working .conf file from Confluence, changing host specific information, and then restarting the JIRA service.
After modifying the vhost.conf file all JIRA content worked as intended.
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot