Reverse Proxy and Port-forwarding limitation with Jira Align Self-Hosted setup

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

This article describes the limitation of reverse proxies and port-forwarding on Jira Align self-hosted instances

Solution

  • Jira Align does not support different port numbers between reverse proxy/port-forwarding appliances and the port binded on the Jira Align IIS.

  • Port number used on the reverse proxy/port forwarder has to be same as the port used for binding on IIS of the Jira Align server

  • Example of non-supported configuration: Reverse proxy/port-forwarding appliance has port 443 and the IIS is binded to port 8443 on Jira Align server

  • Example of supported configuration: Reverse proxy/port-forwarding appliance has port 443 and the IIS is binded to port on same port 443 on Jira Align server

Updated on April 14, 2025

Still need help?

The Atlassian Community is here for you.