Split ssh configuration fails in 4.2.4

User Support General
, ,
1

I have been using the setup from the Split SSH guide here and it has recently stopped working.

From what I can tell it may have still been working when I switched templates from fedora-41-xfce to fedora-42-xfce but as of right now, I can’t run git pull origin main. It instead seems to timeout, with the following message displayed:

$ git pull origin main
ssh: connect to host github.com port 22: Connection timed out
fatal: Could not read from remote repository.

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

When I tried initial troubleshooting as suggested in this discussion, ssh -T git@github.com gives the following:

$ ssh -T git@github.com
ssh: connect to host github.com port 22: Connection timed out

I am able to run ssh-add -L successfully (it lists the correct key with the corresponding description)

The solution in the linked discussion says:

Resolved by disabling and masking gcr-ssh-agent and using a non-gui ssh agent in the ssh backend (vault) vm instead.

I’ve looked around the forum and I am none the wiser regarding what this means or how I can go about doing this. If someone could point me in the right direction, I would be much obliged. Thank you in advance :pray:

2

So I have tried to disable this using the answer here (doing the opposite of course) and seemed fine but I am not sure how to use a “non-gui ssh agent” in the ssh backend (vault) vm instead.

3

The error here is a timeout. It looks like either the qube has no network access or it has access but cannot access git.github.com.

1 Like
4

Thanks so much for taking the time to respond here :pray:

Indeed it seems it can’t access github.com via port 22. Using this gist, I’ve changed my ~/.ssh/config to the following:

Host github.com
  Hostname ssh.github.com
  Port 443

and then using this comment in the original Split SSH guide, I’ve modified it to:

Host github.com
  Hostname ssh.github.com
  Port 443
  IdentityAgent "/home/user/.SSH_AGENT_vault"

where the .SSH_AGENT_vault would be the name of the vault vm. I was able to get the GUI prompt but of course, it may stop working by the time I get to 4.3 or hopefully it will be fixed by then :upside_down_face:

1 Like