Good day,

Not sure if this helps you, but after adjusting all of these settings I found this under the "Git" section:

The default it seems is to use the "Embedded" version, this ignores any of the system settings that the instructions dictate. Switching this to "System" allowed 1Password to act as the SSH Agent. :)

rctneil I haven't used SourceTree, but a few things to double check that have caught me in the past:

• Run git config --list to make sure your Git user matches the user and SSH key you are offering to GitHub (https://developer.1password.com/docs/ssh/git-commit-signing#step-1-configure-git-commit-signing-with-ssh)
• Double check to make sure your SSH keys are in your Private vault. I assume they are, but if they aren't, you would need to update the SSH agent config
• Do you have multiple SSH keys in the vault? The SSH agent picks the first one and then runs through them all until one works. This can cause some hosts to reject the keys. If you do, you may need to configure the SSH agent to match your key to a specific host. (https://developer.1password.com/docs/ssh/agent/advanced/#ssh-server-six-key-limit

This is driving me INSANE!!!!

What the heck is going on?

I've basically sat and researched this for the majority of the day and can't for the life of me figure out what's going on.

In Tower I try pushing or pulling from a remote repo and I get the error above. The repo's are mine and I have full access to them.

My key is correctly added to Github, it's in 1Password in my Private vault and also shows up when I run ssh-add -l.

If I test in terminal ssh -T git@github.com, this also works fine.

Sourcetree is also still not seeing the keys.

My SSH config file looks like:

Host *
IdentityAgent "~/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sock"

and the 1Password config file looks like:

`# This is the 1Password SSH agent config file, which allows you to customize the

behavior of the SSH agent running on this machine.

You can use it to:

* Enable keys from other vaults than the Private vault

* Control the order in which keys are offered to SSH servers

EXAMPLE

By default, all keys in your Private vault(s) are enabled:

[[ssh-keys]]

vault = "Private"

You can enable more keys by adding more [[ssh-keys]] entries.

For example, to first enable item "My SSH Key" from "My Custom Vault":

[[ssh-keys]]

item = "My SSH Key"

vault = "My Custom Vault"

[[ssh-keys]]

vault = "Private"

You can test the result by running:

SSH_AUTH_SOCK=~/Library/Group\ Containers/2BUA8C4S2C.com.1password/t/agent.sock ssh-add -l

More examples can be found here:

https://developer.1password.com/docs/ssh/agent/config

[[ssh-keys]]
vault = "Private"`

Please can someone help?!!! I'm desperate here!

Something really weird is going on. I've followed all the instructions online but still not working. I tried Git Tower too and when I try to pull or push from / to my repo's I get error like:

The key is on my GitHub account. If I run ssh-add -l then I see my three keys from 1Password listed.

What's going on? I just want to get this sorted.