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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bitbucket Webhook to Jenkins returns 503


I have a webhook set up at When Bitbucket sends the webhook I'm getting a 503 response. Jenkins is installed on a Windows Server. I'm able to get to my Jenkins install just fine from

2 answers

I am running into the same issue, i keep getting 503 error from Bitbucket to Jenkins webhook.  i have whitelisted all outbound IP's listed in this document

Any suggestions? 

Thank you in advance

0 votes
jredmond Atlassian Team Jan 02, 2019

Does your Jenkins system permit inbound requests from Bitbucket's IPs?

I have the following inbound firewall rule;


- TCP 8080


- Remote IP address

Here is the webhook request log info;

Type: repo:push
Event time: a few seconds ago (Wednesday, January 2nd 2019, 2:43:24 pm)
Request attempts: 1 (retry pending)
Response from
HTTP status: 503
Elapsed time: 5974ms
Request time: a few seconds ago (Wednesday, January 2nd 2019, 2:43:30 pm)

Content-Length    3162
Via    1.1 (squid)
X-Cache    MISS from
Content-Language    en
X-Squid-Error    ERR_CONNECT_FAIL 110
X-Cache-Lookup    MISS from
Vary    Accept-Language
Server    squid
Connection    keep-alive
Date    Wed, 02 Jan 2019 19:56:55 GMT
Content-Type    text/html;charset=utf-8
Mime-Version    1.0

Like Deleted user likes this
jredmond Atlassian Team Jan 02, 2019

Those are the inbound addresses - what Jenkins would use if it connects *to* Bitbucket. You need to whitelist the outbound addresses, since webhooks are connections *from* Bitbucket.

Like nruiz likes this

I've found bitbucket ip's here.

Are you saying to add the following as an inbound firewall rule on my windows server? I tried this and still get the same 503.


Also, this is an AWS EC2 instance. I tried adding the above IPs to the security group as All TCP,,, (added /32 to end of last two).

Like nicnei likes this

I'm getting closer. I added another rule to my AWS inbound security group;

All TCP, Any IP


I now get status 200 but am concerned with this rule since it allows any IP.

Deleted user Aug 29, 2019

Interesting! I am having the same issue, @Vincent Roggero did you manage to understand what IPs you had to whitelist? I have added the one published by bitbucket but didn't have any luck

If you use aws check the security group.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

3,755 views 10 16
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you