Hello All, New to the community. i have moved our servers into a colocation space. I was given a static IP by our ISP, but for some reason, i cannot get to bitbucket.com from the assigned IP. Tracert and MTR all come back clean. DNS is resolving correctly, i can ping all day long, but when I open up bitbucket.org, i get an http2 error page. i know it is not internal, as I have hooked up a laptop directly to the incoming ISP port and assigned the static. It fails. When I hook the same laptop to a different ISP or hotspot, i can get to it. The ISP says bitbucket may be blocking the subnet. Anyone have any ideas or suggestions?
Hi @Michael Longo,
Can you please confirm if you have trouble accessing Bitbucket Cloud (https://bitbucket.org/)?
I am asking because you mention bitbucket.com and I also don't see a Bitbucket Cloud account in our system with the same email as your community account.
If you are indeed having issues with Bitbucket Cloud, I can create a support ticket for you that will be visible only to you and Atlassian staff. You can then share in the ticket the static IP you are using, and the support team can check if it's blacklisted.
Welcome to the Community!!
The IP is used only for whitelisting so that traffic is allowed. Even though you can ping the resolution at a later time may happen to different IP and the one which you were reaching out to becomes obsolete.
Use the Domain itself to reach out to the site.
Here's a list of inbound dynamic IP list that Atlassian has provided
Thank you for the reply. We have ruled out internal routing issues by hooking a laptop directly to our ISP. With no firewall (Physical or software), and no network equipment in front of the connection, we still can't get to the site. We then installed a software VPN on the machine we were originally trying to connect from (with all network/firewall equipment in place), and were able to get to the site, and run our codes with it active. This leads us to believe either our ISP is blocking traffic upstream somewhere (although they claim they aren't), or the newly assigned IP block we were given is listed on a DoS attack list somewhere.