How to fix 503 Error code from Webhooks response

Summary

The user receives a 503 error code from Webhooks response even if the Webhook IPs are allowlisted for the inbound connection at their end.

Diagnosis

Try to connect to Webhook URL through Atlassian Bitbucket Proxy:

Cause

If we are unable to connect to Webhook URL using the above command (HTTP/1.1 503 Service Unavailable) that means one of the following:

• Bitbucket IPs are not allowlisted as Inbound traffic at the user end;

• The IPs are allowlisted, but the port on which Webhook is running is not open for the inbound traffic.

Solution

Confirm that the following IPs are allowlisted as Inbound traffic:

Additionally, confirm these IPs are open for the port on which Webhook URL is running.

• This could be done using the nmap command.