Troubleshooting SSH

Sometimes, firewalls refuse to allow SSH connections entirely. If using HTTPS cloning with credential caching is not an option, you can attempt to clone using an SSH connection made over the HTTPS port. Most firewall rules should allow this, but proxy servers may interfere.

If you've lost your SSH key passphrase, depending on the operating system you use, you may either recover it or you may need to generate a new SSH key passphrase.

As a security precaution, GitHub automatically deletes SSH keys that haven't been used in a year.

As a security precaution, SSH keeps track of which hosts it has previously seen.

A "Permission denied" error means that the server rejected your connection. There could be several reasons why, and the most common examples are explained below.

This error usually means you were unable to connect to the server. Often this is caused by firewalls and proxy servers.

This error occurs when you try to add a key that's already been added to another account or repository.

This error means the key you are pushing with is attached to an account which does not have access to the repository.

This error means the key you are pushing with is attached to another repository as a deploy key, and does not have access to the repository you are trying to push to.

In rare circumstances, connecting to GitHub Enterprise Cloud via SSH on Linux produces the error "Agent admitted failure to sign using the key". Follow these steps to resolve the problem.

This error means your version of ssh-add does not support macOS keychain integration, which allows you to store your passphrase in the keychain.

This error means your CA root certificate is out of date. If your CA root certificate needs to be updated, you won't be able to push or pull from GitHub Enterprise Cloud repositories.

This error means that the SSH key type you used was unrecognized or is unsupported by your SSH client.

This error means the SSH key you're using to perform a Git operation is unverified.