1
0
mirror of synced 2025-12-21 10:57:10 -05:00
Files
docs/content/github/authenticating-to-github/testing-your-ssh-connection.md
Jason Etcovitch caaee7a124 Update all files to use {% data %} (#15253)
* Add back changes from prior to purge

* Manually fix some invalid Liquid

* Updoot render-content

* Improve test messages to show correct output

* Run el scripto

* Pass the remaining test
2020-09-29 16:01:04 -04:00

2.5 KiB

title, intro, redirect_from, versions
title intro redirect_from versions
Testing your SSH connection After you've set up your SSH key and added it to your {% data variables.product.product_name %} account, you can test your connection.
/articles/testing-your-ssh-connection
free-pro-team enterprise-server
* *

Before testing your SSH connection, you should have:

When you test your connection, you'll need to authenticate this action using your password, which is the SSH key passphrase you created earlier. For more information on working with SSH key passphrases, see "Working with SSH key passphrases".

{% data reusables.command_line.open_the_multi_os_terminal %} 2. Enter the following:

$ ssh -T git@{% data variables.command_line.codeblock %}
# Attempts to ssh to {% data variables.product.product_name %}

You may see a warning like this:

> The authenticity of host '{% data variables.command_line.codeblock %} (IP ADDRESS)' can't be established.
> RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
> Are you sure you want to continue connecting (yes/no)?

or like this:

> The authenticity of host '{% data variables.command_line.codeblock %} (IP ADDRESS)' can't be established.
> RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
> Are you sure you want to continue connecting (yes/no)?
  1. Verify that the fingerprint in the message you see matches one of the messages in step 2, then type yes:
> Hi <em>username</em>! You've successfully authenticated, but GitHub does not
> provide shell access.

{% linux %}

You may see this error message:

...
Agent admitted failure to sign using the key.
debug1: No more authentication methods to try.
Permission denied (publickey).

This is a known problem with certain Linux distributions. For more information, see "Error: Agent admitted failure to sign".

{% endlinux %}

  1. Verify that the resulting message contains your username. If you receive a "permission denied" message, see "Error: Permission denied (publickey)".