ERR_CONNECT_FAIL 110 in Webhooks connection

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Diagnosis

You attempt to use the Webhooks functionality, but your endpoint is not receiving the Webhooks requests due to the following error in the HTTP response payload:

X-Squid-Error: ERR_CONNECT_FAIL 110

This error indicates that the TCP connection to the destination server was not successful and will therefore need to be troubleshooted further.

Procedure

A potential cause behind this issue is that your proxy/firewall settings are incorrect and are actively blocking connections from Bitbucket. To troubleshoot this, you can attempt the following:

  1. Whitelist our IP addresses in your corporate firewall on the destination server

  2. Review Squid proxy ACL documentation and allow bitbucket.org/related IP addresses above on the destination server

  3. Follow our article for troubleshooting network issues to determine where exactly the connection is failing

As Squid proxy is a third-party product - this is not supported by Atlassian and will instead require further support from Squid. If you have contacted Squid already and have been advised that the issue is being caused by Bitbucket Cloud please feel free to raise a support ticket or raise a community support ticket for further assistance. 

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.