Unable to edit or delete Jira Webhook configuration due to error

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

Problem

Trying to edit or delete a Jira Webhook configuration results in the following error in the UI: <p>Status: 0 : error

(Auto-migrated image: description temporarily unavailable)

Diagnosis

Environment

  • Jira instance running behind a proxy or load balancer

Diagnostic Steps

  • HTTP/s connection in Jira/Tomcat's server.xml configuration file is not configured with the correct proxyName or proxyPort attributes, despite being accessed through a proxy.

Cause

  • Wrongly configured Tomcat connector. Tomcat is not configured to be aware of it's proxy name and port.

  • Or Jira is not being accessed with the correct URL.

Solution

Workaround

The resolution below requires a restart. If you're unable to restart right away, you might be able to remove or edit the webhooks using the API endpoints for the Webhooks plugin described in https://developer.atlassian.com/server/jira/platform/webhooks.

Resolution

  1. Edit the $jira-installation-directory/conf/server.xml configuration file

  2. Find the proxy connector used to access Jira and add the following attributes, proxyName="your.domain.com" proxyPort="443"

    as described under the *Configure Tomcat* section of all our proxy integration documentation e.g. https://confluence.atlassian.com/adminjiraserver/integrating-jira-with-apache-using-ssl-938847754.html. See example below

1 <Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="8080" protocol="HTTP/1.1" redirectPort="8443" useBodyEncodingForURI="true" scheme="https" proxyName="your.domain.com" proxyPort="443"/>
    • Please remember to replace your.domain.com with your actual Base URL (which should be your proxy hostname too).

    • Note that if you're accessing Jira over plain http and not https your proxyPort is more likely be ="80" instead.

Updated on April 11, 2025

Still need help?

The Atlassian Community is here for you.