Public or private URLs for applications links?

[joshua kugler]

When configuring application links (in this case between JIRA and Confluence) is the URL entered one that has to be accessible publically, or can it be one that only the server can access. That is, from JIRA, can I give a URL for Confluence of http://localhost:8081, or do I need to use its public, canonical URL?

Our situation is this:

We have our JIRA app server behind a load balancer. The App server cannot contact the load balancer. I tried to configure the application link with the external address, But that URL actually points to a load balancer, and the firewall prevents the app server from contacting the load balancer, so configuring the app links fails. The application (Confluence in this case) is running on the same app server a JIRA. Can I just use the localhsot URL for the application link (as well as the application link from Confluence to JIRA)?

[Ryan Goodwin · Accepted solution]

Hi Joshua,

You will want to use both in this case. For the application URL, you can use the localhost. For the display url, use the publicly accessible url.

For information describing these fields, you can view the documentation here:

Editing an Application Link

If this resolves your question, please accept it as an Answer. Hope this helps!

[Joshua Kugler]

Got it! When I configured the Link, I used the application URL (localhost:NNNN) and it automatically pulled the display URL (http://wiki.domain.com) as part of the Link creation process. Didn't even realize that. Which explains why it works.

Thank you very much!

[EddieW]

Joshua, please go ahead and accept Ryan's answer. This question is shwo to still be looking for an answer, and will draw other users away from helping those with outstanding questions.

[joshua kugler]

I wanted to, but have been working with Atlassian to try to get two of my accounts merged correctly. I've marked it answered now.

[loyx]

Great, this is what I needed for jira, confluence, stash etc running behind Nginx as a reverse proxy... The SSL endpoint is Nginx and from there, inside the server (yes I'm running everything in the same box cos we are just a team of 7), everything runs with http.

Thanks!

[EddieW]

Based on my experience you will need to use the URL configured in the tool's configuration for app links authorization to work. We use apache reverse proxy in front of all our tools, and even when they were on the same app server (which we quickly moved away from as each app can get pretty hungry) we still had to use the address of the apache server, which was the address configured in each tool (https://mydomian/jira, not http://hostname:8090/jira)