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 Webhook to Jenkins connection timeout

Hi Team,


I am trying to set-up a bitbucket(cloud) webhook to trigger a Jenkins pipeline, but some have its not working. You can see the error message at the end of this message.


Jenkins Webhook URL :

Jenkins is hosted on our internal network but it have the above public end point which will be accessible only from bitbucket inbound IPs listed below.  These IP ranges are whitelisted in our organisation firewall layer to allow inbound, but still its not working. 

Please let me know if I miss anything here. 



IPv4 inbound for,, and










body 115:lang(fa) { direction: rtl; font-size: 100%; font-family: Tahoma, Roya, sans-serif; float: right; } 116:lang(he) { direction: rtl; } 117 --></style> 118</head><body id=ERR_CONNECT_FAIL> 119<div id="titles"> 120<h1>ERROR</h1> 121<h2>The requested URL could not be retrieved</h2> 122</div> 123<hr> 124 125<div id="content"> 126<p>The following error was encountered while trying to retrieve the URL: <a href="*">*</a></p> 127 128<blockquote id="error"> 129<p><b>Connection to [unknown] failed.</b></p> 130</blockquote> 131 132<p id="sysmsg">The system returned: <i>(110) Connection timed out</i></p> 133 134<p>The remote host or network may be down. Please try the request again.</p> 135 136<p>Your cache administrator is <a href="mailto:webmaster">webmaster</a>.</p> 137 138<br> 139</div> 140 141<hr> 142<div id="footer"> 143<p>Generated Tue, 15 Nov 2022 22:37:03 GMT by (squid)</p> 144<!-- ERR_CONNECT_FAIL --> 145</div> 146</body></html>



1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 16, 2022

Hi @Pradeep Dumpala,

The IP ranges for webhook delivery are different, as mentioned here:

This includes a link to the following doc:

If you need to whitelist IP addresses only for webhook delivery, you can whitelist the ranges mentioned in Outgoing connections only.

Kind regards,

thank you @Theodora Boudale  for the details. Now I am able to get the firewall allow the inbound from a connectivity perspective.


But its the different issue, the response body is coming as <null response>


Response from https://jenkinsappdev.****.xyz/bitbucket-web-hook/
HTTP status: -2

Request time: 5 minutes ago

<null response>
X-Hook-UUID c7875cd2-a4e4-49e4-941f-f37cf9755beb
X-B3-SpanId 14558d8855ace511
X-B3-Sampled 1
X-B3-TraceId 14558d8855ace511
X-Attempt-Number 1
X-Event-Key repo:push
X-Request-UUID 26d03104-0d9c-456e-bbec-1d3cdf02e20a
User-Agent Bitbucket-Webhooks/2.0
X-Event-Time Wed, 16 Nov 2022 22:23:52 GMT
Content-Type application/json
Please let me know if I am missing something here.

Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 29, 2022

Hi @Pradeep Dumpala,

Apologies for the late reply, I was out of office.

If you go to the Repository setting of the repo on Bitbucket Cloud website > select Webhooks > select Edit for the webhook you created, you will see an option Skip certificate verification. Is this option checked or unchecked?

If it is unchecked, can you check it (temporarily, for testing purposes), and then see if it works properly the next time an event triggers the webhook?

This is to figure out if the <null response> error is related to a problem with the certificate.

Kind regards,

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events