Webhook fails with HTTP 403 Forbidden

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

Jira tries to fire a webhook but gets an HTTP 403 response from the webhook server. 

Environment

This error may occur in Server or DC environments with an outbound proxy.

Diagnosis

  • The Jira logs show a warning with the HTTP code 403 when firing the webhook: 

    1 2020-01-17 06:31:25,837 httpclient-callbacks:thread-93 WARN anonymous [c.a.webhooks.plugin.PublishTaskFactoryImpl$PublishTaskImpl] Client error - 403 when posting to web hook at '<webhook_url>'
  • Check if the webhook host is included in the JVM argument -Dhttp.nonProxyHosts.

    Example

    1 -Dhttp.nonProxyHosts=localhost|127.0.0.1|local.example.com

Cause

Jira is going through the outbound proxy to fire the webhook and the proxy forbids the request.

Solution

Add the webhook host to the JVM argument -Dhttp.nonProxyHosts.

Updated on March 10, 2025

Still need help?

The Atlassian Community is here for you.