Resolving Bitbucket’s ssh DNS hostname

If like me you’re using Bitbucket and you’ve been faced with a number of updates etc, you might find yourself in a situation where it will just fail on you.. despite working the previous day.

The error I would get is the following:

Pushing to ssh://siliconjoe@bitbucket.org:siliconjoe/ppmc.git
ssh: Could not resolve hostname bitbucket.org:siliconjoe: nodename nor servname provided, or not known
fatal: Could not read from remote repository.

huh? I was using this yesterday…

I noticed a small change in the URL for my remote which wasn’t working:

ssh://siliconjoe@bitbucket.org:siliconjoe/ppmc.git

and one which was working as a new repo:

ssh://git@bitbucket.org/siliconjoe/ppmc.git

The fix is the addition of the git@ instead of siliconjoe@ and then also replacing the : with a slash /

Simple, yet could have costed a number of dumb hours.

Like what you read? Give Toby Allen a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.