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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Webhook error (Atlantis Integration)


An Atlantis Server has been setup on EC2 instance and the corresponding URL has been mapped to a DNS. The same URL has been put into the Webhook configuration on Bitbucket and some triggers have been configured. But whenever the events (say: pullrequest) triggers the Atlantis Server running on EC2 instance, it gives -: HTTP 403 "Access control configuration prevents your request from being allowed at this time. Please contact your service provider if you feel this is incorrect." :- error. 

The end requirement for the POC is to Integrate Atlantis with Bitbucket to initiate Terraform plan on pull request.

1 answer

0 votes
Patrik S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 02, 2022

Hello @Mayank Gupta ,

Welcome to Atlassian Community! 

The HTTP 403 error you are receiving means there was some issue with the authentication between bitbucket and your destination server. You have either not provided the credentials in your webhook URL or the credentials were not correct.

Currently in Bitbucket Cloud webooks only support HTTPS basic authentication, and you need to specify the credentials as part of the webhook URL, as the below example : 

https://<username of the destination>:<password of the destination>@<URL of the destination> 

I'd like to point out that e-mail addresses are not currently supported to be used as the username in the webhook's URL, and this is being tracked in the bug ticket BCLOUD-14773 .

Additionally, I'd also like to share that we already have a feature request to include the possibility of adding a secret as part of the webhook configuration to be an alternative method of authentication. You can take a look at that feature request in the following link : 

You can feel free to add your vote there, since this helps both developers and product managers to understand the interest. Also, make sure you add yourself as a watcher in case you want to receive first-hand updates from that ticket. Please note that all features are implemented with this policy in mind.

Hope that helps! Let me know in case you have any questions.

Thank you, @Mayank Gupta .

Kind regards,

Patrik S

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events