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!


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
Community Members
Community Events
Community Groups

How to securely access bitbucket from corporate firewall? Please help in a detailed SOP.


We cannot clone from bitbucket to our system when it is connected to mahindra domain, So please help in a detailed answer which can justify the security concerns of our security team and provide a logical, secured and detailed answer.

The error is as follows:

ssh: Could not resolve hostname Temporary failure in name resolution
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

1 answer

1 vote

Welcome to the Atlassian Community!

Your network team needs to fix the DNS setup of your network.

The error 

ssh: Could not resolve hostname

is telling us that your server simply can't find Bitbucket, and that's because your DNS is not working for that machine.

We are able to curl  when used proxy which is set by the organization. and we are also able to access portal from mahindra domain. We are only facing issue while using git clone. So, is it still the problem of dns only?

while I run https git clone, It shows following error. [ fatal: unable to access '<account>/<repo>' : could not resolve host:] 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events