JIRA Behind IIS - Slow and Base URL issue Edited

Hello,

I have a JIRA instance behind IIS. I've double checked all of the steps on https://confluence.atlassian.com/adminjiraserver/integrating-jira-applications-with-iis-938847749.html

If I access JIRA form the server itself through localhost it works great.

But if I access it externally through the URL it's incredibly slow and it's failing the Base URL check.

Not sure where else to look to see where the bottleneck might be?

Also, related question, if I wanted to circumvent IIS altogether, what would be involved? I tried stopping IIS and then editing the server.xml file to comment out the

<Connector port="8009" enableLookups="false" redirectPort="8443" protocol="AJP/1.3" /> 

line, then restarting the JIRA service. When I do that I cannot access JIRA externally at all, so I believe I am missing a step.

1 answer

0 votes

The bottleneck is obviously something in IIS

The failure of the base url check means Jira cannot find itself on that base url, so IIS is not proxying the connection properly.  You've missed something in the configuration, or your IIS has non-default settings that are breaking it.

I don't know IIS well enough to tell you where to start, although the logs are probably going to tell you something useful.

To run without IIS, you need to remove the connector you configured, and make sure you have a route from your client machine directly to the server.  You should be able to see an error when you say "I cannot access Jira" - what is that?

I mean the browser just gives me a 'connection timed out' error. I am thinking it is a firewall issue to be honest, something I don't have access to configure at the moment.

Ah, ok, it's not slow, you don't get anything.

This implies IIS could be fine, and something else is blocking your access.  As you suspect, a firewall is the most likely thing.

It's slow if IIS is enabled. If IIS is disabled and I am trying to access it through <URL>:8080 it doesn't come up at all.

Sorry, the comment confused me, I thought it was about the direct connection.  Ignore my last comment!

You don't need to disable anything to make the direct connection work, the connector for IIS is in addition to it.

So, there should be a fully functional interface on http://<host>:8080  When you're on the server itself, localhost is the host.

But as you get a connection time out error when connecting from a remote machine, that tells us something is blocking that on your network, or possibly a firewall on the server.

The other route to your Jira goes through IIS and sounds painfully slow.

I would definitely want to check how responsive the direct connection is, but as localhost is fast, I strongly suspect that connection will be fast too.  If it's not, it tells us there's a network problem, rather than IIS.  If it is fast, then it's definitely a problem with IIS.  At that point, I'm afraid I'm stuck - I only know enough IIS to get Atlassian stuff using it as a proxy, I don't know how to debug it being slow.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,847 views 12 18
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot