Skip to main content
Publicamos atualizações frequentes em nossa documentação, e a tradução desta página ainda pode estar em andamento. Para acessar as informações mais atualizadas, visite a Documentação em inglês.
� 

� 

Esta versão do GitHub Enterprise foi descontinuada em 2022-10-12. Nenhum lançamento de patch será feito, mesmo para questões críticas de segurança. Para obter melhor desempenho, segurança aprimorada e novos recursos, atualize para a última versão do GitHub Enterprise. Para obter ajuda com a atualização, entre em contato com o suporte do GitHub Enterprise.

Testing your SSH connection

After you've set up your SSH key and added it to your account on your GitHub Enterprise Server instance, you can test your connection.

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".

  1. Abra TerminalTerminalGit Bash.

  2. Enter the following:

    $ ssh -T git@hostname
# Attempts to ssh to GitHub Enterprise Server

    You may see a warning like this:

    > The authenticity of host 'hostname (IP ADDRESS)' can't be established.
> RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
> Are you sure you want to continue connecting (yes/no)?

  3. Verify that the fingerprint in the message you see matches your enterprise's public key fingerprint. If it does, then type yes:

    > Hi USERNAME! You've successfully authenticated, but GitHub does not
> provide shell access.

    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".

    Note: The remote command should exit with code 1.

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