Git Integration for Jira Self-Managed (Data Center/Server) Documentation

Contact Support
GitKraken Status  

Setup GitLab Server to respond to incoming network API calls

In order for GitLab to display correct repository clone links to your users, it needs to know the URL under which it is reached by your users (e.g.

To reconfigure:

  1. Access the GitLab configuration file in /etc/gitlab/gitlab.rb.

    sudo vi /etc/gitlab/gitlab.rb
  2. Change the external_url value to your GitLab server URL.

    external_url "" #this is the default URL
    external_url "http://X.X.X.X.local/" #change it to your GitLab Server URL
  3. Run the reconfigure command to make the change take effect.

    sudo gitlab-ctl reconfigure


Read this GitLab documentation to know more about configuring the external URL for GitLab.

You should be able to add the GitLab repositories via Git Integration for Jira app ➜ Manage git repositories:



Prev: Getting started for Git administrators (index)

Next: New GitLab v10+ authentication


More related articles on Git for Jira administrators

Setup GitLab Server to respond to incoming network API calls (this page)

New GitLab v10+ authentication

General settings: Improving Jira performance

Adding a repository hosted on Windows Servers or Windows Network Share (Admins)

Setting up repository root not located in Jira Home directory (Admins)

Reindex API to trigger indexing

Recommended reindex interval setting

Setting up web linking

Setting up webhooks

Increasing timeout threshold for large repositories while doing a Git pull

Working with Tracked folders

Recommended upgrade method for Git Integration for Jira

Discard cloned files in Jira Home directory (General setting)

Have feedback about this article? Did we miss something? Let us know!
On this page