Bitbucket Pipeline cannot access own workspace API due to IP allowlist

[Simba Choi]

We have IP allowlist enabled on our Bitbucket Cloud workspace for security purposes. However, we're facing an issue where our Bitbucket Pipeline cannot call the Bitbucket API for the same workspace

Issue Details:

• We have a Pipeline step that fetches PR diff and posts comments using Bitbucket REST API
• The API calls fail with HTTP 403: "To access this repository, an admin must whitelist your IP"

What we tried:

1. Added atlassian-ip-ranges: true and size: 4x to the pipeline step - did not work
2. Checked the outbound IP using curl -s ifconfig.me - confirmed it's not within Atlassian IP ranges

Questions:

1. Is there a way to bypass IP allowlist for API calls made from Pipelines within the same workspace?
2. Why is atlassian-ip-ranges: true not assigning Atlassian IP ranges to our Pipeline?
3. Can Repository Access Tokens be exempted from IP allowlist restrictions?
4. Are there any other solutions for this use case without setting up a self-hosted runner or proxy server?

Thank you for your assistance.

[Ben]

Hi @Simba Choi 

Can you please raise a support ticket so that we may assist you further? We need to check your Pipelines environment/IP configuration settings, but to access this - a formal support ticket is needed for our systems to allow us to grant this access to investigate further:

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

Please let me know if you encounter issues raising the ticket, and I will raise one on your behalf (please share your timezone so I can raise it in the correct region).

Cheers!

- Ben (Bitbucket Cloud Support)