Some Jira functionalities are not working due to the error "The requested URL was rejected. Please consult with your administrator"
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
Some Jira functionalities are not working due to the error "The requested URL was rejected. Please consult with your administrator".
The list below shows some examples of functionalities that are known to be impacted by this error, but please note that this list is not exhaustive. These are just examples:
when clicking on the Start watching this issue button in a Jira issue, the action does not complete and a spinning wheel appears
when pasting an image in a Jira comment, the error "File "image name" was not uploaded" is thrown
editing a workflow scheme name or description does not work
editing customer notification templates in JSM (Jira Service Management) projects, using the menu Edit Templates from Project Settings > Customer Notifications
The purpose of this article is to explain what this error means and how to address it.
Environment
Jira Server/Data Center on any version from 8.0.0.
Diagnosis
Collect a HAR file while replicating any of the issue listed above, and check the URL corresponding to the action that failed in a HAR file analyzer.
For example, if the issue is related to watching a ticket:
Look for an URL similar to <JIRA_BASE_URL>/rest/api/1.0/issues/<ISSUE_ID>/watchers.
When checking HTTP request corresponding to the action that fails, verify that you can make the following observations:
the response code is 200
however, the response contains the following error, which indicates that the request actually failed to reach the Jira application:
1 2 3 4 5 6 7 8 9 10<html> <head> <title>Request Rejected</title> </head> <body>The requested URL was rejected. Please consult with your administrator.<br> <br> Your support ID is: XXXXXXXXXXXXXXXX<br> <br> <a href='javascript:history.back();'>[Go Back]</a></body> </html>
If you see the response above in the HAR file (or by using the Network tab in the browser), then this KB article is relevant.
Another example if with the Customer Notification template functionality (saving the edited templates fails with an error):
Look for an URL similar to JIRA_BASE_URL>/rest/servicedesk/notifications/1/outgoing-email-settings/<PROJECT_ID>/project-template
When checking HTTP request corresponding to the action that fails, verify that you can make the following observations:
the response code is 200
however, the response contains the following error, which indicates that the request actually failed to reach the Jira application:
1 2 3 4 5 6 7 8 9 10<html> <head> <title>Request Rejected</title> </head> <body>An unexpected error occurred. Please contact XXXXXX by email XXXXXX or phone No. XXXXXXX.<br> <br> Your support ID is: XXXXXXXXXXXXXXXX<br> <br> <a href='javascript:history.back();'>[Go Back]</a></body> </html>
Cause
As explained in the Stack Overflow discussion linked here, this error is generated by a Firewall coming from the F5 Proxy Server that the Jira application is configured behind:
Your http is being blocked by a firewall from F5 Networks called Application Security Manager (ASM). It produces messages like: "Please consult with your administrator.", "Your support ID is: xxxxxxxxxxxx". So your application is passing some data that for some reason ASM detects as a threat. Give the support id to your network engineer to learn the specific reason.
In other words, the issue is not coming from the Jira application itself, but it is coming from the F5 proxy server configuration.
Solution
Since this error is happening outside the Jira application, you will need to reach out to your Proxy Server / Network Team to have them look into the error and fix the firewall configuration accordingly.
Was this helpful?