Bitbucket cloud Webhook won't trigger rancher pipeline

[Dmitry Portnoy]

Integrated Bitbucket Cloud with Rancher. I able to see repositories, created rancher pipeline, but it won't trigger automatically if some changes have been made in repo.
Getting error: 

X-Squid-Error ERR_CONNECT_FAIL 110
As per BitBucket support solution, added following IPs to rancher security group  and to route tables  using internet gateway.

IPv4 inbound for bitbucket.org, api.bitbucket.org, and altssh.bitbucket.org 104.192.136.0/21 185.166.140.0/22 18.205.93.0/25 18.234.32.128/25 13.52.5.0/25

 Still doesn't work....... Please, help. Thank you

[Theodora Boudale · Accepted solution]

Hi @Dmitry Portnoy and welcome to the community.

The IP addresses that need to be whitelisted for webhook delivery are different.

On this documentation page there is a section titled "Valid IP addresses for webhook delivery" that has a link to the following page:

• https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/#Outgoing-Connections

You will need to whitelist these IPs for Outgoing Connections.

Kind regards,
Theodora

[Dmitry Portnoy]

Thank you! It works!!

[Theodora Boudale]

That's good to hear and you are very welcome!

Please feel free to reach out if you ever need anything else.

Kind regards,
Theodora