New IP ranges not working

[matthiasbrodelet]

Are the new IP ranges working as mentioned in this article?
https://bitbucket.org/blog/ip-address-update-2024

We have added the new ones and removed the old ones and now we can't deploy anymore with bitbucket pipelines and rsync over SSH.

Are any changes for our end even needed if we only need to SSH into our server from Bitbucket?

Our server has a whitelist of IP's that can get access so we need to whitelist Bitbucket.

[Ben]

Hi @matthiasbrodelet 

Those old IP addresses have not been retired yet and will be active until August 31st, so there's a chance your builds are still trying to use them.

You can verify which IP your pipelines builds are using by executing a check IP command as part of your build script:

• curl http://checkip.amazonaws.com/

I would suggest adding back the old IP addresses and retiring them after August 31st:

• 18.205.93.0/25
• 18.234.32.128/25 
• 13.52.5.0/25

I would also suggest referring to our complete IP whitelisting page for more context regarding our address ranges:

• https://support.atlassian.com/bitbucket-cloud/docs/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall/

Please let me know if any issues/further questions.

Cheers!

- Ben (Bitbucket Cloud Support)