From f93e68ee3a2e23404b80afc5afeb1146e4827e2b Mon Sep 17 00:00:00 2001
From: Anton Smith <asmith@gitlab.com>
Date: Wed, 14 Feb 2024 07:58:33 +0000
Subject: [PATCH] Jira app - mention connect-install-keys can prevent manual
 install

---
 .../settings/jira_cloud_app_troubleshooting.md           | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/doc/administration/settings/jira_cloud_app_troubleshooting.md b/doc/administration/settings/jira_cloud_app_troubleshooting.md
index 1823f8a8d6f6c..a765b12d11e04 100644
--- a/doc/administration/settings/jira_cloud_app_troubleshooting.md
+++ b/doc/administration/settings/jira_cloud_app_troubleshooting.md
@@ -56,6 +56,15 @@ To resolve this issue, disable the **Jira Connect Proxy URL** setting.
   1. Clear the **Jira Connect Proxy URL** text box.
   1. Select **Save changes**.
 
+If the issue persists, verify that your self-managed GitLab instance can connect to
+`connect-install-keys.atlassian.com` to get the public key from Atlassian.
+To test connectivity, run the following command:
+
+```shell
+# A `404` status code is expected because you're not passing a token
+curl --head "https://connect-install-keys.atlassian.com"
+```
+
 ## Data sync fails with `Invalid JWT`
 
 If the GitLab for Jira Cloud app continuously fails to sync data, it may be due to an outdated secret token. Atlassian can send new secret tokens that must be processed and stored by GitLab.
-- 
GitLab