2015-11-26 28 views
9

Bazı nedenlerden dolayı Bitbucket numaralı telefonuma git push gönderemiyorum. Çalışırdı ama artık çalışmıyor ve nedenini anlayamıyorum.Bitbucket git push ssh "conq: geçersiz depo sözdizimi."

$ git push ssh://[email protected]:MyUser/MyGit.git 
conq: invalid repository syntax. 
fatal: Could not read from remote repository. 

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

Bir ssh anahtarını oluşturdum, onu gitbucket'e ekledim. bu şekilde tanımlanır benim ssh-agent:

$ ssh-agent /bin/bash 
$ ssh-add ~/.ssh/id_rsa 
$ ssh-add -l 
    #2048 14:41:6f:c9:06:54:88:6c:89:e2:ba:24:6c:36:10:78 /Users/SomeUser/.ssh/id_rsa (RSA) 

Ayrıca burada

ssh -T [email protected] 
logged in as MyUser. 

You can use git or hg to connect to Bitbucket. Shell access is disabled. 

detaylar Giriş bilgilerimi kontrol:

$ ssh -T -v [email protected] 
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 
debug1: Reading configuration data /home/vagrant/.ssh/config 
debug1: Reading configuration data /etc/ssh/ssh_config 
debug1: /etc/ssh/ssh_config line 19: Applying options for * 
debug1: Connecting to bitbucket.org [131.103.20.167] port 22. 
debug1: Connection established. 
debug1: identity file /home/vagrant/.ssh/id_rsa type 1 
debug1: identity file /home/vagrant/.ssh/id_rsa-cert type -1 
debug1: identity file /home/vagrant/.ssh/id_dsa type -1 
debug1: identity file /home/vagrant/.ssh/id_dsa-cert type -1 
debug1: identity file /home/vagrant/.ssh/id_ecdsa type -1 
debug1: identity file /home/vagrant/.ssh/id_ecdsa-cert type -1 
debug1: identity file /home/vagrant/.ssh/id_ed25519 type -1 
debug1: identity file /home/vagrant/.ssh/id_ed25519-cert type -1 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.2 
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 
debug1: match: OpenSSH_5.3 pat OpenSSH_5* compat 0x0c000000 
debug1: SSH2_MSG_KEXINIT sent 
debug1: SSH2_MSG_KEXINIT received 
debug1: kex: server->client aes128-ctr hmac-md5 none 
debug1: kex: client->server aes128-ctr hmac-md5 none 
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<3072<8192) sent 
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP 
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent 
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY 
debug1: Server host key: RSA 97:8c:2b:f4:6e:14:6b:5c:3b:zc:va:47:48:74:7c:40 
debug1: Host 'bitbucket.org' is known and matches the RSA host key. 
debug1: Found key in /home/vagrant/.ssh/known_hosts:1 
debug1: ssh_rsa_verify: signature correct 
debug1: SSH2_MSG_NEWKEYS sent 
debug1: expecting SSH2_MSG_NEWKEYS 
debug1: SSH2_MSG_NEWKEYS received 
debug1: Roaming not allowed by server 
debug1: SSH2_MSG_SERVICE_REQUEST sent 
debug1: SSH2_MSG_SERVICE_ACCEPT received 
debug1: Authentications that can continue: publickey 
debug1: Next authentication method: publickey 
debug1: Offering RSA public key: /home/vagrant/.ssh/id_rsa 
debug1: Remote: Forced command: conq username:MyUser 
debug1: Remote: Port forwarding disabled. 
debug1: Remote: X11 forwarding disabled. 
debug1: Remote: Agent forwarding disabled. 
debug1: Remote: Pty allocation disabled. 
debug1: Server accepts key: pkalg ssh-rsa blen 279 
debug1: Remote: Forced command: conq username:MyUser 
debug1: Remote: Port forwarding disabled. 
debug1: Remote: X11 forwarding disabled. 
debug1: Remote: Agent forwarding disabled. 
debug1: Remote: Pty allocation disabled. 
debug1: Authentication succeeded (publickey). 
Authenticated to bitbucket.org ([131.103.20.167]:22). 
debug1: channel 0: new [client-session] 
debug1: Requesting [email protected] 
debug1: Entering interactive session. 
debug1: Sending environment. 
debug1: Sending env LC_ALL = en_US.UTF-8 
debug1: Sending env LANG = en_US.UTF-8 
logged in as MyUser. 

You can use git or hg to connect to Bitbucket. Shell access is disabled. 
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 
debug1: client_input_channel_req: channel 0 rtype [email protected] reply 0 
debug1: channel 0: free: client-session, nchannels 1 
Transferred: sent 3752, received 3400 bytes, in 0.1 seconds 
Bytes per second: sent 61887.6, received 56081.5 
debug1: Exit status 0 

Benim git remote -v

$ git remote -v 
MyGit [email protected]:MyUser/MyGit (fetch) 
MyGit [email protected]:MyUser/MyGit (push) 

Benim ~/.ssh/config

Host bitbucket-MyGit 
    HostName bitbucket.org 
    User git 
    IdentityFile /home/vagrant/.ssh/id_rsa 
    IdentitiesOnly yes 

Etrafa baktım ama ben yanlış yaptıklarını bulamıyorum. Herhangi bir öneri?

+0

? 'git remote -v' – Donal

+0

@Donal Bu bilgiyi içermesi için düzenleme yaptık – Wistar

+0

Uzaktan kumandanızın şu şekilde görünmesini beklerdim: ssh: //[email protected]/MyUser/MyGit.git – Donal

cevap

27

Bu yanlıştır

$ git push ssh://[email protected]:MyUser/MyGit.git 

Bu doğrudur bu repo kumandalarınızın için ayarladığınız Neler

$ git push ssh://[email protected]/MyUser/MyGit.git 
+4

site üzerindeki kendi otomatik oluşturulan url doğru sözdizimi yok garip: S :( – CasualT

+0

Onların belgeleri – jcollum

+0

omg ağırlaştırıcı - bitbucket üzerinde sh ** kaybetmek üzereydi - Çok teşekkür ederim! –