Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

JIRA Redirect to FQDN

I am running JIRA server 7.13.0 and trying to get a redirect to work from the server shortname to the FQDN without a proxy if possible

Right now users can go to:

https://jira or 

I want everyone on the FQDN so things work as they should with the base url.

I was reading about:

When playing in my lab environment I was not having much success using the urlrewrite. Has anyone had luck this way? Or are people using something like apache?


For confluence (running windows.. for now), I ended up using IIS and do not want to go that route. 

1 answer

1 accepted

2 votes
Answer accepted
Daniel Eads Atlassian Team Apr 09, 2019

Hey Mike,

I definitely get wanting to shy away from IIS. Apache and especially nginx aren't that bad though! They both run on Windows so you could go that route if you wanted before switching over to a Linux server.

After playing around with this a little in a test environment, I was able to get this working with Jira in Tomcat. All that was required was adding a rule to urlrewrite.xml which for Jira is located at:


Below the existing <rule></rule> section in the file, I added the following rule (make sure to update the FDQN to the proper value):

<condition type="scheme" operator="equal">https</condition>
<condition name="host" operator="equal">jira</condition>
<to type="permanent-redirect" last="true">$1</to>

Don't forget to restart Jira after making changes in this file to have them go into effect. And also - make sure you do this on a test environment first!


As mentioned in the documentation you linked to, doing this kind of change in your install directory won't persist across Jira upgrades. It's generally better to do this behind a reverse proxy so that it persists upgrades and is easier to troubleshoot. Pretty easy for this change to get lost in the Jira install path, whereas it's pretty simple to see an nginx config. Some food for thought as you move forward.


Thanks Daniel - This leads me on the right track. Looks like I am getting ERR_TOO_MANY_REDIRECTS now but it is redirecting. Maybe something in my iptable rules is causing it

Edit: I put it on the default port and removed all iptable rules but still getting the too many redirects. Will continue troubleshooting. Thanks

Thanks to your answers I figured out a way to redirect all names not matching the defined base URL.

<condition type="scheme" operator="equal">https</condition>
<condition name="host" operator="notequal"></condition>
<to type="permanent-redirect" last="true">$1</to>

This approach also avoids the ERR_TO_MANY_REDIRECTS.

In my server.xml short names coming via HTTP connector are redirected to HTTPS connector first. So this rule applies also to requests which used HTTP initially.

Like Daniel Eads likes this

I found that you also have to include the query string in the <to> line in order to capture all possible Jira links such as boards and filters, so like this:

<condition type="scheme" operator="equal">https</condition>
<condition name="host" operator="notequal"></condition>
<to type="permanent-redirect" last="true">$1?%{query-string}</to>

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you