Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Bitbucket pipeline: API request return Cloudflare HTML in response

Hello, I'm facing a problem with my pipeline.
I try to make a GET request to my API in the pipeline and expected to receive an API response.
Therefore I receive 403 or 200 with Cloudflare's response.
In my local machine or my docker container all ok. 
API is open.

In Cypress tests situation is the same.
Please help me with that.

Screenshot 2023-02-17 at 12.41.02.png

1 answer

1 accepted

0 votes
Answer accepted
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 20, 2023

Hi @EvoX0 and welcome to the community!

You mentioned that the API call works as expected in your Docker container. Are you running this API call in a Docker container based on the same Docker image as the one specified in your bitbucket-pipelines.yml file for that step?

Are you using the same Bearer token in the Pipelines as the one you use locally in the Docker container?

If the answer to any of the questions is no, could you please try running the API call locally in a Docker container based on the same image (and image tag) as the one in the bitbucket-pipelines.yml file for that step, and also use the same Bearer token; and then let me know if you see the same issue or not?

Kind regards,

Hi, @Theodora Boudale 

The problem is solved, thanks for your reply.
The issue was in Cloudflare protection against bots.

Like Theodora Boudale likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events