Bitbucket Cloud Webhook ERR_CONNECT_FAIL 110

[Andrew Lethcoe]

We had a web hook on push going to an internal jenkins that suddenly stopped last week. We had made no internal network or firewall changes. But the webhook suddenly stopped working Wednesday last week around 10am. 

We are getting this squid error from a 10-18-21-51 which i'm assuming is an ip? Even though it is formatted with dashes. According to the documentation we have all the outgoing ranges listed here in our firewall. Again this was all working for months before last wednesday.

We verified we have these ports in our firewall. https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/#Outgoing-Connections

Anyone have any idea how to track down what changed?

[Ben]

Hi @Andrew Lethcoe 

I can confirm that our IP addresses have not changed recently (as far as webhooks are concerned).

If you've double-checked and ensured that all IP's are whitelisted for the Atlassian summary IPv4 ranges and Atlassian summary IPv6 ranges under the Outgoing connections heading (documentation you linked), but it is still not accepting connections from webhooks - I'd suggest reaching out to a network administrator for further support.

If they check this and believe that the issue is Bitbucket-related - we'll need you to raise a support ticket with our support team using your paid workspace URL. Please let us know if you encounter any issues raising a ticket, and we'll raise one on your behalf :)

• https://support.atlassian.com/contact/ 

Cheers!

- Ben (Bitbucket Cloud Support)