How-To: Troubleshoot EZSSH Issues with GitHub

How to troubleshoot EZSSH not properly authenticating to GitHub and other GitHub related issues that might happen when getting started with GitHub ssh certificate authentication

Common Issues with the ezssh CLI for GitHub

Authentication Errors Troubleshooting

  1. Make sure to run ezzshh git before running your Git Commands
  2. Make sure your git repository is on the Git organization that trusts EZSSH
  3. Make sure you have the right access to the repository.

Permission Denied (publickey) Error on Windows

If when you run:

 ssh YOURGITORGADDRESS

you are able to authenticate. But when you run any git operation you get the following error:

YOURGITORGADDRESS: Permission denied (publickey).

fatal: Could not read from remote repository.

Please make sure you have the correct access rights

This is because Windows Git can be setup on installation to use its own SSH-Agent instead of using the Windows one. To fix this problem you will have to change your git installation to use the windows SSH-Agent. To do this run:

git config --global core.sshCommand "'C:\Windows\System32\OpenSSH\ssh.exe'"

For changes to take effect, you might have to close your terminal, and in some cases a reboot is necessary.

Common Issues when Setting Up EZSSH for GitHub

GitHub App used by EZSSH does not have the correct permissions

If you see the following error:

The GitHub App used by EZSSH does not have the correct permissions

This is usually caused by your SAML mapping token not having the correct permissions. To fix this, you will have to generate a new token with the correct permissions. Make sure to Single Sign On (SSO) your token if your organization uses SSO. Refer to this guide for more information.