JIRA 7 has landed! Are you an existing JIRA user with questions about upgrading? Visit the Migration Hub for information about upgrading to new JIRA applications

Skip to end of metadata
Go to start of metadata

Unable to render {include} The included page could not be found.


On a JIRA instance using Apache Web Server, some links contain the actual host name and port the application is running on, rather than JIRA's configured Server Base URL. This can cause the links to be unreachable because of intervening firewalls or DNS resolution configurations as the BaseURL matches the VirtualHost alias of the presentation proxy.

For example, the base URL is

  • http://example.com/jira

but link URLs point to

  • http://tomcat01:8180/jira/



This is usually caused by the VirtualHost configuration section in Apache httpd does not specify the ProxyPreserveHost directive. This would instruct Apache to relay requests towards the internal server using the hostname provided by the client. This in turn will provide Tomcat with the correct DNS name for the ServletRequest.getServerName method used by JIRA to build URL links in the generated HTML response.


This JIRA documentation page configuring mod_proxy provides a working example of a configuration enabling the required ProxyPreserveHost directive.

1 Comment

  1. KY

    ProxyPerserveHost is wrongly spelled.

    It's ProxyPreserveHost. Please fix it. Thanks.