I am having difficulty with connecting my local gitlab server to Jira software.
I have followed all the documentation I can find but cannot seem to get it to link.
Using the GitLab for Jira (gitlab.com) app from the Jira Marketplace
When entering https of my server, I get the error ‘Failed to update GitLab version. Please try again.’
When entering http of my server, it seems like it is working and shows the ‘sign in’ button, then followed by ‘Failed to load Jira Connect Application ID. Please try again.’
{"errors":{"instance_url":["Could not be installed on the instance. Error response code 401"]}}
No explanation, why it cannot be installed, nothing.
And yes it works with http, but then you cannot login. Will check whether cloudflare has anything to do with it. Because it seems like request is proxied via gitlab.com.
But later on once you try to sing in to self-hosted gitlab, you get when this request runs:
Hi,
I was strugling with this too untill i found this documentation page
Adding Jira Connect Application ID solves the problem.
Remember that If your GitLab instance is self-managed, you must follow some extra steps to install the GitLab.com for Jira Cloud app, and your GitLab instance must be accessible by Jira.
If you have already tried installing App from Atlassian Marketplace the extra steps will fail and you have to follow this troubleshooting steps.
Any ideas why this happens? Does gitlab.com proxy remove the header or it is not added by the code, that prepares the request. Can someone give me a link to this extensions latest version source code?
Wonder if the gitlab.com proxy removes this token header or something else is a miss or application does not add that header to gitlab group api search endpoint request?
Thank you for following up on this. However, I’ve read the latest instructions provided in your new doc (GitLab for Jira Cloud app | GitLab) but I’m still encountering errors when connecting our self-managed gitlab.
I’ve checked and updated the settings in our gitlab as described here (GitLab for Jira Cloud app | GitLab), meaning, I’ve added our instance name in the redirect URI and I’ve removed the Jira Connect Proxy URL (which was set to gitlab.com). Still seeing the same error.
I even tried with the proxy in place, but no luck.
Any thoughts as to what I’m doing wrong?
I use Google Chrome and I’ve been enabling feature flags with our infra team in one attempt couple of weeks ago.
Same issue here (Jira Cloud with “GitLab for Jira (gitlab.com)” v1.0.16-AC + self-hosted Gitlab v15.7.6):
Trying to complete the first-time configuration at https://.atlassian.net/plugins/servlet/ac/gitlab-jira-connect-gitlab.com/gitlab-configuration fails with “Failed to update GitLab version. Please try again.”.
A network capture on our self-hosted Gitlab instance shows reproducibly, that the proxy at gitlab.com closes the connection, because it cannot verify our certificate, which is issued by “Sectigo RSA Domain Validation Secure Server CA”:
“TLSv1.3 Record Layer: Alert (Level: Fatal, Description: Unknown CA)”
Since we have no control over the certificate store at gitlab.com, it would be good to know at least, which CAs are considered as trusted, that we have a chance to issue another certificate from such a CA.