Unable to edit or delete Jira Webhook configuration due to error
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Problem
Trying to edit or delete a Jira Webhook configuration results in the following error in the UI: <p>Status: 0 : error
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.
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
- Edit the $jira-installation-directory/conf/server.xml configuration file
- 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
<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.