git & bitbucket: no address associated with name

Hi Guys,

I'm having some trouble setting up git with bitbucket. I'm new to git so any help would be much appreciated. I'm on a Windows 7 machine running the Git bash as installed from the default install (haven't used anything fancy etc).

I've followed the "Set up SSH for Git" guide and all the steps seemed to complete OK, however, when I try to push to my git repo I get the following error message:

$ git push -u origin master
ssh: bitcuket.org: no address associated with name
fatal: Could not read from remote repository.

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

I've done the suggested checks, like making sure my id was added to the ssh key list and that the ssh connection is okay... seems ok?

$ ssh -T git@bitbucket.org
conq: logged in as james_hume.

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

The only thing that differs to the guide is that t says my username rather than my bitbucket account. Is this significant? If so, do you know how I can fix this please?

Any advice would be great, thank you.

Further info, just in case

$ git --version
git version 1.8.1.msysgit.1

$ cat .git/config
[core]
        repositoryformatversion = 0
        filemode = false
        bare = false
        logallrefupdates = true
        symlinks = false
        ignorecase = true
        hideDotFiles = dotGitOnly
[remote "origin"]
        url = git@bitcuket.org:my_name/my_repo.git
        fetch = +refs/heads/*:refs/remotes/origin/*
[gui]
        wmstate = zoomed
        geometry = 887x427+200+200 171 192

James

2 answers

1 accepted

Looks like you have a minor typo there:

url = git@bitcuket.org:my_name/my_repo.git

What is the result if you fix that?

Hi Marcus,

Thanks for replying... what was the typo? If you meant "my_name" and "my_repo" they were just replacements... was pretty useless replacing the user name, not sure why I felt the need to... silly really.

I've just fixed it though... what it was was that I had initially used a "deployment key", not realising what it was. I should have added a key to my account. Having done that I had to re-create a copy of the repo as somehow "origin" had been messed up. Once I did that things are now working.

Thanks for taking the time though :)

Regards,

James

You had mispelled bitbucket as bitcuket.

Doh! That couldn't have helped and explains why the second attempt worked and must be why the first one, along with the deployment key issue, didn't. Thanks marcus...

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

2,044 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you