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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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
4,555,634
Community Members
 
Community Events
184
Community Groups

unable to access 'https://bitbucket.org/Onports/*****************.git/': Failed to connect to b

After running "git pull origin master" on EC2 instance i am getting this error .

fatal : unable to access 'https://bitbucket.org/Onports/***************.git/': Failed to connect to bitbucket.org port 443 after 130674 ms: Connection timed out.

1 answer

0 votes
Mateus T
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 11, 2022

Hi @aaquibmemon,

Welcome to the Atlassian Community!

It looks like your machine is not able to properly connect to Bitbucket.org on port 443. In this case, there are a series of factors that could be causing this issue:

  1. Check if the issue persists while using SSH protocols and pulling from your repository. If SSH works fine, you might be having an issue with your internal firewalls blocking our connections on port 443;
  2. Make sure that your EC2 instance has all Bitbucket Cloud IPs and Domains whitelisted;
  3. You can also run the Git Clone with a verbose output in order to get more details on this issue and share the output here with us. Make sure to remove any sensitive information from the logs output before posting it on this public thread.
$ GIT_CURL_VERBOSE=1 GIT_TRACE=1 git pull origin master

Cheers,

Mateus T

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events