How to setup múltiple SSH configurations with Bitbucket and Git

I'm working with different projects using two different Bitbucket accounts. My SSH config file looks like this:

# account 1
Host bitbucket.org
    User user1
    IdentityFile ~/.ssh/id_rsa_1

# account 2
Host bitbucket.org
    User user2
    IdentityFile ~/.ssh/id_rsa_2

If I git push (or pull or whatever) to/from account 2, I get an error because it tries to connect using account 1 config.

I also tried this:

# account 1
Host account1
    HostName bitbucket.org
    User user1
    IdentityFile ~/.ssh/id_rsa_1

# account 2
Host account2
    HostName bitbucket.org
    User user2
    IdentityFile ~/.ssh/id_rsa_2

But I get the same error. How can I configure it so it tries with all the configurations until find the right one?

Using SSH config may not accomplish what you expect it to when connecting to the same host. You're better off bypassing that altogether. The better approach is to simply tell Git how you wish to connect and let it handle everything for you using the GIT_SSH_COMMAND environment variable or the core.sshCommand config setting to supply the SSH command line for your repo to use. Full examples are found in this answer.

https://superuser.com/a/912281/98717

You should also double check your SSH settings. Generally, git repos are accessed by the git user.

Here's the text of the answer linked above as it exists at the time of this answer. Credit to the original user.

Environment variable GIT_SSH_COMMAND

From Git version 2.3.0, you can use the environment variable GIT_SSH_COMMAND like this:

GIT_SSH_COMMAND="ssh -i ~/.ssh/id_rsa_example" git clone example

Note that -i can sometimes be overridden by your config file, in which case, you should give SSH an empty config file, like this:

GIT_SSH_COMMAND="ssh -i ~/.ssh/id_rsa_example -F /dev/null" git clone git@github.com:example/example.git

Configuration core.sshCommand

Since Git version 2.10.0, you can configure this per repo or globally, using the core.sshCommand setting. There's no more need to use the environment variable. Here's how you clone a repo and set this configuration at the same time:

git clone -c "core.sshCommand=ssh -i ~/.ssh/id_rsa_example -F /dev/null" git@github.com:example/example.git
cd example/
git pull
git push

If the repo already exists, run:

git config core.sshCommand "ssh -i ~/.ssh/id_rsa_example -F /dev/null"

The configuration is saved in .git/config

The second ~/.ssh/config approach - the one where you have Host account1 and Host account2 - is usually easiest to work with once it's set up, but I didn't see anything in your post about actually using the new names in those repos. (Note that your first approach won't work: since the Host values are identical, it's impossible for the SSH client to know which one it should use in a given situation.)

For repos you already have, git remote set-url origin account1:owner/repo or git remote set-url origin account2:owner/repo will update the remotes to use the parameters defined in ~/.ssh/config.

For repos you haven't cloned yet, instead of git clone git@bitbucket.org:owner/repo, use either git clone account1:owner/repo or git clone account2:owner/repo.

Once you've set the remote URLs as appropriate, then git fetch, git pull, git push, and any other network operations will use the parameters you've defined in ~/.ssh/config. You won't have to change the commands, and if you need to change anything about the setup for one account (such as defining a new key or port) then you can do it once, for all affected repos, in ~/.ssh/config.