Git error: conq: repository does not exist

Question

I'm getting the following errors in Git using BitBucket:

conq: repository does not exist.
fatal: The remote end hung up unexpectedly

How do I rectify this issue? I've carried out the following:

git init .   
git remote add origin git@bitbucket.org:myname/myproject.git
git add .
git commit -m "..."

git push  <<< error occurs here

I've set-up BitBucket with the ssh key and repo is shown on dashboard.

Side node: I got this because VSCode thought it would be smart and replaced my spaces with `%20`'s; then as a result it was trying to execute a clone of my local file path instead of the repo name... — Andrew, Nov 17 '20 at 22:36

score 39 · Answer 1 · edited Mar 05 '15 at 20:08

39

In my case, the git repository was duplicated somehow in the config file:

cat .git/config

gave me:

[remote "origin"]
    url = git@bitbucket.org:myUserName/myRepositoryName.git/myRepositoryName.git
    fetch = +refs/heads/*:refs/remotes/origin/*

As you can see, myRepositoryName is duplicated, so I removed that, and now the config file looks like this:

[remote "origin"]
    url = git@bitbucket.org:myUserName/myRepositoryName.git
    fetch = +refs/heads/*:refs/remotes/origin/*

Doing this, my problem is solved. Now the push is correctly done. Hope this help someone.

edited Mar 05 '15 at 20:08

Jonathan Hall

75,165
16
143
189

answered Nov 27 '12 at 20:28

Malloc

15,434
34
105
192

I changed the remote repository and in order to fix this I also had to removed the `/shared/cached-copy` folder. – Darme Mar 10 '15 at 15:46

score 28 · Answer 2 · answered Jan 26 '14 at 20:02

28

This error also occur when you rename your repo:

Edit .git/config and change from:

git remote add origin git@bitbucket.org:myname/myproject.git

to:

git remote add origin git@bitbucket.org:myname/my_new_project_name.git

answered Jan 26 '14 at 20:02

Igor Parra

10,214
10
69
101

1

Exactly my problem, Thanks @lgor for help – Khayam Gondal Oct 28 '14 at 17:29
Or when you change your username. `git@bitbucket.org:name/project.git` `git@bitbucket.org:new_name/project.git` – Aust Dec 31 '14 at 03:42
This happened to me as well. I transfer my repo to my organization, and this worked for me. Thanks! – Sebastialonso Mar 04 '15 at 14:43
@IgorParra can't believe I forgot. Edit: oh, I remember why I forgot, not enough rep :/ – Sebastialonso Mar 05 '15 at 14:24

score 15 · Answer 3 · answered Oct 16 '13 at 13:19

15

git remote rm origin
git remote add origin git@github_or_bitbucket_or_whatever_link

answered Oct 16 '13 at 13:19

hasentopf

755
1
12
27

score 15 · Accepted Answer · answered Jan 30 '12 at 18:59

15

I managed to do this in the end by removing the origin and re-adding it. Everything seemed ok after I did this.

answered Jan 30 '12 at 18:59

jaffa

26,770
50
178
289

1

what do you mean by "removing the origin" exactly? – Berry Tsakala Mar 01 '13 at 23:51
nevermind. My bug was different =(i'll write it in a separate answer) – Berry Tsakala Mar 01 '13 at 23:57
Also for me it works. Remove origin with "git origin rm namebranch" and re-add with "git origin add bitbucketlink". Good! – Nothing Jun 04 '14 at 08:28
Sharing [my answer](http://stackoverflow.com/a/34270097/2404470) for future readers – Zameer Ansari Dec 14 '15 at 14:59

score 3 · Answer 5 · answered Apr 15 '14 at 01:28

I had a similar problem, and this thread helped me solve the issue, but my solution is slightly different:

I was on a remote server, so first I had to change into the public_html (www) directory, then initialize the repo. (note you have to first add your .ssh key in bitbucket)

$ git init

which initialized an empty Git repository

then add the remote

$ git remote add origin git@bitbucket.org:myname/myproject.git

then I was able to pull and checkout my branch

$ git pull
$ git checkout <branch-name>

Martin Geisler · Answer 6 · 2012-01-19T14:25:45.580

3

You get this error if the remote repository hasn't been created. Bitbucket is running a service called conq that handles pushes and you see the error message from it. Simply create a new (empty) repository and the push should succeed.

Here I'm pushing to a non-existing repository:

$ git push git@bitbucket.org:mg/testt.git master
conq: repository does not exist.
fatal: The remote end hung up unexpectedly

and here I push to the correct path:

$ git push git@bitbucket.org:mg/test.git master
Counting objects: 3, done.
Writing objects: 100% (3/3), 203 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: bb/acl: mg is allowed. accepted payload.
To git@bitbucket.org:mg/gtest.git
 * [new branch]      master -> master

The test repository was newly created on Bitbucket. If the problem persists, then I suggest deleting the empty repo from Bitbucket and re-creating it.

edited Jan 19 '12 at 14:25

answered Jan 19 '12 at 13:49

Martin Geisler

72,968
25
171
229

Strange... I've just double checked and I get exactly the error you describe when I push to a non-existent repository. – Martin Geisler Jan 19 '12 at 14:26
Is this anything to do with SOPA? – jaffa Jan 19 '12 at 14:27
No, Bitbucket didn't participate in the blackout yesterday. – Martin Geisler Jan 19 '12 at 14:28
If I use git push on its own it doesn't work. If I use push with the whole origin path it works. Weird? Is this a bitbucket bug? – jaffa Jan 19 '12 at 14:33
I can push into a new repo with `git push origin master` and with `git push master. Maybe you were just unlucky and they had a small glitch. – Martin Geisler Jan 19 '12 at 14:40
Hi Martin, "git fetch origin master" failed with the same error. What gives with this? – jaffa Jan 20 '12 at 16:19

score 2 · Answer 7 · edited May 06 '15 at 08:06

Did you encounter this error doing the Rails Tutorial?

I did. And I'm very new to this so I was only doing was the tutorial explicitly told me to do. That got me into trouble because in chapter 3 it says it’s a good idea to create a new repository at Bitbucket and push it up but it doesn't hold your hand through the process like it does in Chapter 2.

Don't forget to create the new repository at BitBucket before pushing to that repository.

From Chapter 2: You should also create a new repository by clicking on the “Create” button at Bitbucket.

I did that and it fixed the problem.

score 2 · Answer 8 · answered Oct 27 '16 at 07:18

In my case, i changed the repo name. Therefore, i was not able to push because changing repo name also changed repo remote url. Thus,

First remove previous remote url by git remote rm origin now add new one and do push.

Hope it'll help someone. Cheers!

score 1 · Answer 9 · answered Mar 02 '13 at 00:05

in my case, i mixed up usernames:

in my scenario there are 2 accounts: i need to connect using my-account to the repository's owner-account:

owner-acc   - created, maintaining the account
my-acc           - me, a participant

the syntax in this case should be

url = git@bitbucket.org:owner-acc/repo-name.git

and NOT my username, nor my account-name.

I assume bitbucket's instructions I followed previously took care of identifying me somehow (it's probably relating my-account with the public key i uploaded earlier).

score 1 · Answer 10 · answered Jan 05 '15 at 05:05

I had this error when trying to deploy with Capistrano.

I was missing the deploy key for that Bitbucket repo.

Here's how to solve the issue:

Generate an SSH Key on your server: https://confluence.atlassian.com/display/STASH/Creating+SSH+keys
Follow these instructions to get ssh-agent running, and load in the identity you just created: https://confluence.atlassian.com/display/BITBUCKET/Troubleshoot+SSH+Issues

Once that's finished just go to the Bitbucket repo > Settings > Deploy Keys and copy and paste your newly created key.

score 0 · Answer 11 · answered Sep 01 '16 at 01:37

0

In some cases (maybe not yours) you may have to change

url = git@guthub.com:username/projectname.git/

to

url = https://github.com/username/projectname.git/

using the Nano editor, say:

nano .git/config

answered Sep 01 '16 at 01:37

Bjørn Kjos-Hanssen

764
7
21

score 0 · Answer 12 · answered Sep 04 '16 at 09:33

In my last case it was all related to capitals in the repo name in Bitbucket. Even when the repository name had capitals, Bitbucket was telling me to use lower case names in the git commands to push initial code. This could be related to git case handling and unix/windows case handling. Just check this if your project name has upper case letters.

score 0 · Answer 13 · edited Apr 13 '17 at 12:36

0

I was able to solve this problem by navigating into the submodule's root directory and using the following command.

git push -v origin master

I stumbled across this at here which also has some other troubleshooting steps that may be of use.

edited Apr 13 '17 at 12:36

Community

1
1

answered Apr 04 '17 at 15:03

pat8719

1,700
1
26
47

score 0 · Answer 14 · answered Apr 25 '23 at 18:44

0

My case is that the PC has saved someone's password which can't access to that repo. delete the saved credential to use jenkins' credential or grant credit to him.

That works for me.

answered Apr 25 '23 at 18:44

Andy

434
5
7

Git error: conq: repository does not exist

14 Answers14

Linked