Setting up jira on Windows 2008 R2

Hi Guys,

I'm fairly new to the world of jira and have relatively little experience with Tomcat etc. I have a windows 2008 R2 virtual server box, which I want to run jira on over port 80. The server has two ip addresses assigned one of which I want to use for jira.

  1. I set up the DNS of the domain name I want to use to point to this IP address, and waited for it to resolve over the internet.
  2. I uninstalled IIS (at some point in the future I need IIS back on the box, at which point I will get it to bind to the other ip address)
  3. I stopped the web deployment agent service (which I belive binds to port 80)
  4. I stopped windows firewall (at some point this needs to be switched back on) by issuing:
    netsh advfirewall set AllProfiles state off
  5. In installed jira as a windows service with a SQL Server database, and modified the server.xml as follows:
    <?xml version="1.0" encoding="utf-8"?>
       Atlassian JIRA Standalone Edition Tomcat Configuration.
       See the following for more information
      Licensed to the Apache Software Foundation (ASF) under one or more
      contributor license agreements.  See the NOTICE file distributed with
      this work for additional information regarding copyright ownership.
      The ASF licenses this file to You under the Apache License, Version 2.0
      (the "License"); you may not use this file except in compliance with
      the License.  You may obtain a copy of the License at

      Unless required by applicable law or agreed to in writing, software
      distributed under the License is distributed on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
      See the License for the specific language governing permissions and
      limitations under the License.
    <Server port="8005" shutdown="SHUTDOWN">
        <!--APR library loader. Documentation at /docs/apr.html -->
        <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on"/>
        <!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
        <Listener className="org.apache.catalina.core.JasperListener"/>
        <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"/>
        <!-- Global JNDI resources
             Documentation at /docs/jndi-resources-howto.html
        <!-- A "Service" is a collection of one or more "Connectors" that share
            a single "Container" Note:  A "Service" is not itself a "Container",
            so you may not define subcomponents such as "Valves" at this level.
            Documentation at /docs/config/service.html
        <Service name="Catalina">
            <Connector port="80"
            To run JIRA via HTTPS:
                 * Uncomment the Connector below
                 * Execute:
                     %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
                     $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA  (Unix)
                   with a password value of "changeit" for both the certificate and the keystore itself.
                 * If you are on JDK1.3 or earlier, download and install JSSE 1.0.2 or later, and put the JAR files into
                 * Restart and visit https://localhost:8443/
                 For more info, see :
                <Connector port="8443" protocol="org.apache.coyote.http11.Http11Protocol"
                  maxHttpHeaderSize="8192" SSLEnabled="true"
                  maxThreads="150" minSpareThreads="25"
                  enableLookups="false" disableUploadTimeout="true"
                  acceptCount="100" scheme="https" secure="true"
                  clientAuth="false" sslProtocol="TLS" useBodyEncodingForURI="true"/>
             If you have Apache AJP Connector (mod_ajp) as a proxy in front of JIRA you should uncomment the following connector configuration line
             See the following for more information :
                  <Connector port="8009" redirectPort="8443" enableLookups="false" protocol="AJP/1.3" URIEncoding="UTF-8"/>
            <Engine name="Catalina" defaultHost="">
                <Host name="" appBase="webapps" unpackWARs="true" autoDeploy="true">
    <Context path="" docBase="${catalina.home}/atlassian-jira" reloadable="false" useHttpOnly="true"> <!-- ==================================================================================== Note, you no longer configure your database driver or connection parameters here. These are configured through the UI during application setup. ==================================================================================== --> <Resource name="UserTransaction" auth="Container" type="javax.transaction.UserTransaction" factory="org.objectweb.jotm.UserTransactionFactory" jotm.timeout="60"/> <Manager pathname=""/> </Context> </Host> <!-- ==================================================================================== Access Logging. This should produce access_log.<date> files in the 'logs' directory. The output access log lies has the following fields : IP Request_Id User Timestamp "HTTP_Method URL Protocol_Version" HTTP_Status_Code ResponseSize_in_Bytes RequestTime_In_Millis Referer User_Agent ASESSIONID eg : 1243466536012x12x1 admin [28/May/2009:09:22:17 +1000] "GET /jira/secure/admin/jira/IndexProgress.jspa?taskId=1 HTTP/1.1" 200 24267 1070 "" "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/2009042523 Ubuntu/9.04 (jaunty) Firefox/3.0.10" "C2C99B632EE0F41E90F8EF7A201F6A78" NOTES: The RequestId is a millis_since_epoch plus request number plus number of concurrent users The Request time is in milliseconds The ASESSIONID is an hash of the JSESSIONID and hence is safe to publish within logs. A session cannot be reconstructed from it. See for more information on Tomcat Access Log Valves ==================================================================================== --> <Valve className="org.apache.catalina.valves.AccessLogValve" resolveHosts="false" pattern="%a %{}r %{jira.request.username}r %t &quot;%m %U%q %H&quot; %s %b %D &quot;%{Referer}i&quot; &quot;%{User-Agent}i&quot; &quot;%{}r&quot;"/> </Engine> </Service> </Server>
    When I start the service I can access the url on the server itself, but trying to access it externally does not work. What I am missing here?
    Any help would be much apprecaited.
    Many thanks,

9 answers

This widget could not be displayed.
Timothy Chin Community Champion Feb 25, 2013

And you try to resolve the domain name externally, does it return a proper result?

This widget could not be displayed.

Yes, if you mean by pinging?

Wouldn't the fact that jira works locally with the domain name proove that it is resolving? The DNS for this domain is not on this server.

Can you tell me if my server.xml is set up correctly?

This widget could not be displayed.
Joe Clark Atlassian Team Feb 25, 2013


^ Is this the local IP address of the interface on the server that you want Tomcat to bind to when listening?

This widget could not be displayed.
Yes that's the IP address
This widget could not be displayed.
Joe Clark Atlassian Team Feb 25, 2013

Ah, well I guess that rules out the obvious problems :-)

Can you provide more description on how it does not work? Do you know what kind of error page you are seeing? It might help identify the cause.

This widget could not be displayed.

When I browse to the URL from an external site, the browser spins for a while and then (IE for example) says cannot display the web page. However if I use the same URL internally it works fine.

I have also tried using (configuring jira to use) the IP address instead of the DNS name, and have also tried a multitutde of ports all of which have the same result.

I can PM you more details if you want to take a look for yourself...

This widget could not be displayed.
Joe Clark Atlassian Team Feb 26, 2013

OK, try running "netstat -a -n -b" on your Windows server after starting Confluence/Tomcat, which will show you all active TCP listeners on your server. Make sure that the tomcat.exe process has successfully bound to the correct IP address and port. Eg, you should see something like this in the output:

Proto Local Address Foreign Address State RpcSs
TCP LISTENING [tomcat.exe]

Assuming that's all good, try opening TCP Port 80 from a remote server using the telnet command. This will check that the port is actually accessible externally. Run "telnet 80" from a bash prompt, and you should get a telnet prompt if it connects successfully. Eg.

jclark@bluetongue ~
$ telnet 80
Connected to
Escape character is '^]'.

I assume that one of these two commands will fail, and we can dig further from there :)

This widget could not be displayed.
Thanks Joseph finally managed to track it down. Looks like there was an SMS service that was hogging port 80 on that IP address. It also looks like the firewall was still playing a part even though I had issued the command stated above to stop it. Once I killed both of these it all started working.
This widget could not be displayed.
Joe Clark Atlassian Team Feb 26, 2013

Nice! Glad we got to the bottom of it :)

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Aug 06, 2018 in Jira Service Desk

A is for Activate: Share your top Jira Service Desk onboarding tips for new users!

Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :).  In the spirit of this month's  august-challenge, we're sourcing stories of Jira Service Desk activation fro...

573 views 25 15
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