@@ -221,6 +221,9 @@ For the second log, you might have one of the following scenarios:
-`json.jira_status_code` and `json.jira_body` might contain the response received from the self-managed instance or a proxy in front of the instance.
- If `json.jira_status_code` is `401 Unauthorized` and `json.jira_body` is `(empty)`:
-[**Jira Connect Proxy URL**](jira_cloud_app.md#set-up-your-instance) might not be set to `https://gitlab.com`.
- The self-managed instance might be blocking outgoing connections. Ensure that the self-managed instance can connect to `connect-install-keys.atlassian.com`.
- The self-managed instance is unable to decrypt the JWT token from Jira. [From GitLab 16.11](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147234),
the [`exceptions_json.log`](../logs/index.md#exceptions_jsonlog) contains more information about the error.
- If a [reverse proxy](jira_cloud_app.md#using-a-reverse-proxy) is in front of your self-managed instance,
the `Host` header sent to the self-managed instance might not match the reverse proxy FQDN.
Check the [Workhorse logs](../logs/index.md#workhorse-logs) on the self-managed instance:
