I have the following inbound firewall rule;
- TCP 8080
- Remote IP address
Here is the webhook request log info;
Event time: a few seconds ago (Wednesday, January 2nd 2019, 2:43:24 pm)
Request attempts: 1 (retry pending)
Response from http://18.104.22.168:8080/bitbucket-hook/
HTTP status: 503
Elapsed time: 5974ms
Request time: a few seconds ago (Wednesday, January 2nd 2019, 2:43:30 pm)
Via 1.1 ip-10-125-126-79.net.atlassian.com (squid)
X-Cache MISS from ip-10-125-126-79.net.atlassian.com
X-Squid-Error ERR_CONNECT_FAIL 110
X-Cache-Lookup MISS from ip-10-125-126-79.net.atlassian.com:8080
Date Wed, 02 Jan 2019 19:56:55 GMT
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, 22.214.171.124/21, 126.96.36.199/32, 188.8.131.52/32 (added /32 to end of last two).
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 https://support.atlassian.com/bitbucket-cloud/docs/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall/
Thank you in advance
Hi everyone, We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...
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