Jira Fails due to Encountered a 403 Forbidden error loading this page

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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

The content on this page relates to platforms which are not supported. Consequently, Atlassian Support cannot guarantee providing any support for it. Please be aware that this material is provided for your information only and using it is done so at your own risk.

When accessing Jira in the browser after starting up, it fails and displays the following error:

1 2 Forbidden (403) Encountered a 403 - Forbidden error while loading this page.

Solution

Jira Behind Proxy with Basic Auth

The cause is that the Jira instance is sitting behind a proxy and using basic authentication.

To fix it, add the line, RequestHeader unset Authorization, to the Apache proxy configuration block to remove the authorization header.

1 2 3 4 5 6 <Location /jira> RequestHeader unset Authorization ProxyPreserveHost On ProxyPass /jira http://otherhost/jira ProxyPassReverse /jira http://otherhost/jira </Location>

ℹ️ Don't forget to add themod_headers module, otherwise, the authorization header may not work properly.

Updated on April 7, 2025

Still need help?

The Atlassian Community is here for you.