Missed Team ’24? Catch up on announcements here.

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

«fatal: Could not read from remote repository» when cloning public repo

Björn Gohla
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 29, 2018

I have the following issue: i created a public repository https://bitbucket.org/bgohla/stupidtest/src/master/ . When I try to clone it to my local machine I get:

13:47:54 mgohla@titanic ~ $ git clone git@bitbucket.org:bgohla/stupidtest.git
Cloning into 'stupidtest'...
Connection to bitbucket.org closed by remote host.
fatal: Could not read from remote repository.

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

 SSH access is working as per:

13:24:44 mgohla@titanic ~ $ ssh -v git@bitbucket.org
OpenSSH_7.7p1, OpenSSL 1.0.2o  27 Mar 2018
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to bitbucket.org [18.205.93.0] port 22.
debug1: Connection established.
[...]
debug1: Server accepts key: pkalg ssh-dss blen 434
debug1: Authentication succeeded (publickey).
Authenticated to bitbucket.org ([18.205.93.0]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: pledge: network
debug1: Sending environment.
debug1: Sending env LANG = en_US.utf8
PTY allocation request failed on channel 0
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
logged in as bgohla.

You can use git or hg to connect to Bitbucket. Shell access is disabled.
debug1: channel 0: free: client-session, nchannels 1
Connection to bitbucket.org closed.
Transferred: sent 3064, received 2004 bytes, in 0.4 seconds
Bytes per second: sent 7628.5, received 4989.4
debug1: Exit status 0

What am I doing wrong?

1 answer

0 votes
Björn Gohla
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 29, 2018

retrying after a few hours the problem has disappeared

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events