From d1d715571b8ae88b1096f6c5ab8ef57a471e8ca3 Mon Sep 17 00:00:00 2001
From: Junyi Wang <41598492+ky1ew@users.noreply.github.com>
Date: Thu, 27 Aug 2026 21:04:32 +0800
Subject: [PATCH] docs: specify custom SSH key file in troubleshooting

---
 .../error-permission-denied-publickey.md                    | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md b/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md
index fc569e308b03..0d5fd22df7b1 100644
--- a/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md
+++ b/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md
@@ -141,6 +141,12 @@ You can also check that the key is being used by trying to connect to `git@{% da
 ssh -vT git@{% data variables.product.product_url %}
 ```
 
+If you use a private key with a non-default file name, use the `-i` option to specify the path to the key:
+
+```shell copy
+ssh -i ~/.ssh/KEY-FILE -vT git@{% data variables.product.product_url %}
+```
+
 You'll see output like this:
 
 ```shell