Jira address loading Tomcat7 index.html

I was able to access JIRA via http://localhost:8080 until I tried to follow the steps listed in Integrating JIRA with Apache. Now I get the default page for Tomcat that says:

"It Works!

If you're seeing this page via a web browser, it means you've setup Tomcat successfully. Congratulations!

This is the default Tomcat home page. It can be found on the local filesystem at: /var/lib/tomcat7/webapps/ROOT/index.html"

My goal is to expose my JIRA instance to folks outside of my firewall.  I have set up a subdomain (which doesn't work but seems to be a seperate issue) to point to my JIRA address.  When testing the subdomain and discovering it doesn't work I attempted to test the address that used to work prior to Tomcat setup and hit the Tomcat default page.

I'm sure its a setting in my Tomcat7 and/or Apach2 config but I can't find the switch to flip.  Can someone help me out or at least point me in a direction?  Thanks ahead of time, gurus!

2 answers

1 accepted

1 vote
Accepted answer

If you have installed JIRA and then installed an additional Tomcat instance, then these 2 instances are probably conflicting.   JIRA is being served by its built-in Tomcat, while the one you installed is only serving the default root webapp (which is what displays the "It works!" page).   First, stop and remove the Tomcat that you installed.   Then locate the conf/server.xml in the directory where you installed JIRA.   If you apply your changes there, then you should have much better results.

That's what I get for not reading every line; did not realize jira had its own tomcat.

Have you tried browsing to http://localhost:8080/jira  ?   If you're connecting to 8080 then you're probably bypassing the proxy, and if you're not specifying the path /jira, then the message you're seeing is expected (it's the default Tomcat root webapp).   

The answer would be in your server.xml.   The path you're specifying needs to match the path attribute of the <Context> element for jira.

http://localhost:8080/jira doesn't work either. I skipped step two of the instructions as it said to skip if you won't be using a context path. My JIRA instance will be accessed via http://jira.domain.com.

I see. These instructions could be a bit more clear. First you need to figure out the URL where Tomcat is serving JIRA. Having done that, you can then customise the subdomain and hide the context path as you like. Is Tomcat serving JIRA perhaps from the 8081 port, for example at either http://localhost:8081/ or http://localhost:8081/jira/ ?

It doesn't appear to be. My settings are a straight copy/paste from the instructions with only the proxyName being changed: {code:xml} <Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="8080" protocol="HTTP/1.1" redirectPort="8443" useBodyEncodingForURI="true" proxyName="jira.rairsoft.com" proxyPort="80"/> <Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="8081" protocol="HTTP/1.1" redirectPort="8443" useBodyEncodingForURI="true"/> {code} If I comment out that stuff and uncomment the original settings: {code:xml} <Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" URIEncoding="UTF-8" redirectPort="8443" /> {code} Then I can get to it via http://localhost:8080. I did forget to mention that Tomcat7 was installed after JIRA. This setup is on a new box and as a newbie to JIRA I didn't know it installed Tomcat along with itself (at least I read that over the last couple of days). So I installed JIRA and then Tomcat7. Not sure if that has anything to do with this.

Yes, that's very likely the cause of your trouble. I've posted a separate, more concise answer.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,301 views 12 19
Read article

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