Skip to content

Add additional troubleshooting for non-standard SSH keyfile name #42109

@kmanwar89

Description

@kmanwar89

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/authentication/troubleshooting-ssh/error-permission-denied-publickey

What changes are you suggesting?

This proposed edit is to include steps to specify the exact key filename as part of the ssh -vT [email protected] command while troubleshooting SSH connection issues. This resolves the issue of a user experiencing a [email protected]: Permission denied (publickey). error while following the linked troubleshooting article if they chose to use a non-default filename for their keyfile.

The expected outcome is a user will have clarity on how to specify the SSH keyfile while troubleshooting, preventing false-positive error messages that detract from the original troubleshooting flow.

I'll be opening a PR momentarily that links to this issue, per process.

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    contentThis issue or pull request belongs to the Docs Content teamtriageDo not begin working on this issue until triaged by the team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions