Some actions in Jira cannot be executed due to the error "406 (not acceptable)"
Platform Notice: Data Center Only - This article only applies to Atlassian apps 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
Some actions in Jira cannot be executed due to the error "406 (not acceptable)". The list below shows some examples of actions that might be impacted by this user, but please note that this list is not exhaustive:
Request creation on the Service Desk Customer Portal
Loading of gadgets on Jira dashboards
Usage of some Jira API end points
Deletion of SCRUM boards
Accessing the Jira application via its base URL
Environment
Jira Software (or Jira Service Management) Server / Data Center, on any version.
Diagnosis
Jira is running behind a reverse proxy server such as Apache/Nagios, AND/OR behind a WAF (Web Application Firewall) such as VMware/Signal Sciences
When bypassing the Reverse Proxy Server, or disabling the blocks from the WAF, the issue goes away
When collecting a HAR file while replicating the 406 error, either the following message might be found in the HAR file. ⚠️ Note that, depending on how the proxy server or the WAF is configured, it is also possible that not message will be shown in the HAR file.
Example 1:
<div class="error-page__header-name"> VMware NSX ALB (Avi) </div> </div> ... <h3>406 Response Code</h3> <h3>Please contact our technical support with Request ID: XXX-XXXX-XXX and Application Name: <SOME-APPLICATION> </h3>Example 2:
<html> <head> <title>406 Not Acceptable</title> </head> <body> <h1>Not Acceptable</h1> <p>An appropriate representation of the requested resource <SOME-RESOURCE> could not be found on this server.</p> </body> </html>
Cause
The 406 error is thrown by a web application which is located between the browser (where the request came from) and the Jira application, which could be:
either a reverse proxy server (Apache/Nagios, etc...)
or a WAF (VMware, Signal Sciences)
Solution
The solution will depend on the web application that triggered the 406 error. We recommend to reach out to the administrator of the proxy server (or WAF) to review the error and modify the configuration of server accordingly.
Was this helpful?