How to change the base URL in Windows Server 2012 with IIS?

Jessica Torres_xe0jiy

Hi there, I've searched for the answer to this question and I just can't find it. I have recently installed Jira on a Windows 2012 server running IIS. The default installation had my Jira site running on http://localhost:8080 but I wanted to change that URL so I created an A record pointed to the IP address of my server (like I do with all my other sites) and changed the base URL in the Jira admin settings. There are 2 problems that have arised:

1. I still can only connect through port 8080. So now my URL looks like: http://jira.domain.org:8080. I'd like to know how to remove the port specification.

2. The second problem is that I'm getting a Gadget feed URL error in the health check that I just don't know how to fix. I've read plenty documentation and forums on this and it just isn't clear to me how to do this in my environment.

Any help would be greatly appreciated.

Daniel Eads

Hi Jessica,

Thanks for including all the helpful info in your post! I think we can get you squared away pretty quickly.

1. Jira listens on 8080 by default and generally relies on a reverse proxy (IIS in your case) to pick up traffic on port 80 or 443 for SSL/TLS and forward the requests to Jira on 8080. Here's our document for getting this configured in IIS. To highlight just the bits you need:
   • You don't have a context path, so safely ignore anything referencing a context path in that document
   • Doesn't sound like you're using SSL/TLS, so you can skip those sections as well (although it's a good idea to configure this long-term)
   • You'll need to add this to your server.xml file in Jira's install directory - the document will list more info but these are the relevant lines you'll need to add in the existing connector:
     

      proxyName="jira.<domain>.org"
      proxyPort="80"
      scheme="http"/>

   • Completely follow the instructions in this section of the document to configure IIS.
2. The gadget feed URL will likely resolve itself once Jira and IIS are configured to work with each other. The healthcheck tries to see if the base URL (hopefully set to jira.domain.org) works - if you still need to set up IIS to listen on port 80, the healthcheck is going to fail and throw the error you're seeing. Resolving #1 should take care of this!

Cheers,
Daniel