Problem to solve
I am attempting to integrate Jira with an onsite, self-managed (free) Gitlab installation. The option being pursed is setting up a Private App in Jira for the Gitlab. While a Private App is now listed the setup fails when attempting to ‘Get Started’ with this app.
Steps to reproduce
First attempted was the Atlassian Marketplace Gitlab for Jira Cloud, using the instructions/documentation from Gitlab docs.gitlab.com/administration/settings/jira_cloud_app This process failed to complete when at the final step to link the two applications a “Failed to update the Gitlab instance” message. I have reviewed the posts here that reference this error, but none of them or the troubleshooting steps they referenced assisted.
This lead to pursing the alternative of creating a Private App on Jira for the Gitlab integration. In Jira, the App is listed under Manage Apps, and to complete the setup (the three ellipses) to ‘Get Started’ is chosen. This fails and results in a ‘Contact (Jira) Support’, they have been. However I am investigating all options since I am not eliminating our setup as the issue.
Configuration
General logical layout
Jira ↔︎ Firewall ↔︎ NAT to NGINX reverse proxy ↔︎ Gitlab (container)
443 ↔︎ 443 ↔︎ 5443 ↔︎ 5443
public.URL ↔︎ public.URL ↔︎ proxy to internal.URL ↔︎ internal.URL
The two configurations in Gitlab are
Admin Area > Applications > Instance OAuth applications > Callback URL
h t t p s://public.URL/-/jira_connect/oauth_callbacks
Admin Area > General > Settings > GitLab for Jira App >
Jira Connection Application Id : <value copied from OAuth setup.
Jira Connection Proxy URL :
Jira Connect Additional Audience URL: h t t p s://public.URL
The internal GitLab server can be reach by the internal.URL, the IP address of the proxy server, or the FQDN hostname of the proxy server. The assumption here is that the proxy configuration is working as needed.
Using the public.URL to define the Jira Private App failed, but the internal.URL worked after making a CNAME in DNS to the public IP. This is unexpected.
Are there additional setting(s) in Gitlab that control how it responds to external request?
Are the Gitlab values that been set for the integration to Jira correct? A RTM, and a later RTFM, review of the installation instructions & troubleshooting steps seem to support the settings.
Versions
- X - Self-managed GitLab 17.11