Setting up 8443 to 443 for JIRA

[Craig Moran]

Hi -

We recently installed JIRA and opened it up for public access.  We are also using SSL.  Currently, the link works for any user who is not connected to our private network (eg: https://myjirasite.com).  However, when a user is inside our network, the 8443 port must be included in the url (eg: https://myjirasite.com:8443).  Otherwise, the link will not work.  JIRA is installed on a Windows 2008 R2 server, with IIS 7.5.  I followed these instructions -- https://confluence.atlassian.com/adminjiraserver071/integrating-jira-applications-with-iis-802593039.html#IntegratingJIRAapplicationswithIIS-acceptrequests -- but they did not resolve the issue.  I still need to include the port number in the URL.  Any help would be appreciated.

[Nic Brough -Adaptavist-]

This suggests you have a proxy which catches the external requests and takes the users to your server, but your internal network is routing directly to the server, and not proxying anything.

Four options spring to mind. 

1. Get your internal network to resolve to the proxy instead of the direct link, so the proxy can do its rewriting. 
2. Put a proxy on the JIRA machine (note the disavantage is that you'll now be proxying twice for external users, which can do odd things)
3. Put a proxy on another machine and change the network to land on that instead of the JIRA server.
4. Change the JIRA service to run on port 443 and change the external proxy to expect that

Your choice here depends primarily on how your network team want to handle it!

[Craig Moran]

Thanks for the response, Nic.  I'll discuss this with the network team.

[Craig Moran]

Changing the service to run on port 443, and changing the external proxy resolved the issue.  Thanks again!