I have JIRA 6.2.7 and Confluence 5.5.3 running on a same machine in LAN that behind a firewall, and the firewall has configured two NAT ports so that users can access the server from internet.
WANIP:8080 --> LANIP:8080 (JIRA)
WANIP:8090 --> LANIP:8090 (Confluence)
No other ports are mapped from internet to LAN. I modified their server context path so that the base url of them are:
and users can access them from above links.
Now I am trying to creat application links for them.
Problem 1: When creating application link in JIRA, I provide the confluence base URL (the WANIP access link)
the JIRA system just notify that there is no response from the link I provied. It seems that the system need to acees other ports of confluence from WANIP to LAN when creating application link.
Question 1: Must I map any other ports from WANIP to LANIP on firewall to make JIRA talk to Confluence?
Since the two systems are running on a same machine, so I use localhost(http://localhost:8090/conf) instead of the WANIP when creating applicaiton link and it works.
JIRA also creating a Application Link in the top left corner of the header and use the display link it detected(http://WANIP:8090/conf). so that users can quickly access confluence from it.
Problem2: When I did the same steps in Confluence, tried to create application link in Confluence to JIRA(use http://localhost:8080/jira), Confluence did created applicaition link but It used the application link I provided when creating Application Navigator link although it display correct Display link (http://WANIP:8080/jira)
As a result, the Application Navigator link in Conflucne does not work for those users acess Confluence from internet. It just point to their localhost.
Is It a Confluence bug? and..how to resolve this?
thanks a lot.
Hi there, so regarding your questions, there's no other port you need to open to create the application links. You just need to make sure the applications can talk one each other over the URL you provided.
One other thing that may break the application link is when the application can't access the manifest of the other application, this information is used to define the application link configurtion during the creating process. You can check this information in the following URL's (just edit the base URL to yours):
As for the Application Navigator, this functionality retrieve the URL in the column Display URL of your application link configuration (see here), this URL is defined during the creation of the application link, but your can edit it after that.
I hope it helps.
Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...
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!
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