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,461,221
Community Members
 
Community Events
176
Community Groups

Can't access repositories over SSH

I'm trying to set up a new SSH key to access my repositories. I think I've done everything correctly, but I can't actually access anything.

Running "" ends with the following:

debug1: Authentication succeeded (publickey).
Authenticated to bitbucket.org ([104.192.141.1]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: pledge: filesystem full
debug1: Sending environment.
debug1: channel 0: setting env LANG = "en_AU.UTF-8"
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 3572, received 2212 bytes, in 10.2 seconds
Bytes per second: sent 349.8, received 216.6
debug1: Exit status -1

I think it should be saying something along the lines of "you can use git to connect to bitbucket", but I don't, and then get the following when I try to clone a repo:

fatal: Could not read from remote repository.

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

What am I missing? 

1 answer

Not really a complete answer, but this had something to do with my network. All worked fine once I connected to a VPN. A bit strange.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events