Skip to main content
Table of Contents

GitLab Server (On-Prem) Connection Guide

LinearB's paid plans support connecting to on-premises Git servers, including GitLab Server (On-Prem).

Steven Silverstone
Updated by Steven Silverstone

Follow the steps below to establish the connection.

1. Select GitLab Server as Your Git provider

  1. Navigate to Settings > Company Settings, and select the Git tab.
  2. Click Add Integration and choose GitLab Server as your Git provider.

2. Allowing LinearB Access

If your GitLab Server instance is accessible from the public internet, skip this step.

If your GitLab Server is hosted within a private network, you must allow LinearB's public IP addresses in your firewall:

  • 52.15.80.85
  • 54.241.87.26
  • 54.193.121.186
  • 18.118.232.229

For networks behind a VPN, ensure that a reverse proxy allows LinearB-specific access to GitLab Server.

Understanding IP Allowlisting for gitStream
When configuring IP allowlists in GitLab, you control which external IP addresses can interact with your repositories and APIs. This is important for both the LinearB/gitStream integration and any CI/CD runners in use.

There are two scenarios where this applies:

1. Webhook Event Handling by gitStream
When GitLab sends a webhook (e.g., when a merge request is opened), gitStream may make follow-up API calls—such as retrieving metadata, posting comments, or updating PR statuses. These originate from LinearB’s IP addresses (listed above), so they must be allowlisted to avoid connectivity issues.

2. Outbound Requests from CI/CD Runners
If gitStream is used in your pipeline (e.g., via GitHub Actions or other runners), the runner may also make outbound calls (e.g., clone repo, retrieve commit history). If these runners are hosted on dynamic infrastructure (such as GitHub-hosted runners), their IPs can change frequently—causing blocked access if not allowlisted.

Recommended Solutions:
• Add LinearB’s static IPs (above) to your GitLab allowlist.
• Use self-hosted runners with fixed IPs so their addresses can be allowlisted explicitly.

This ensures gitStream can operate reliably during both automation and pipeline execution.

3. Insert Your GitLab Server URL

  1. After allowing LinearB’s IPs, enter your GitLab Server URL.
  2. LinearB will automatically check connectivity.
  3. Once verified, click Continue and proceed to the next step.

4. Create a Personal Access Token

  1. Log in to GitLab Server and click your avatar in the upper-right corner.
  2. Select Settings from the dropdown menu.
  1. In the User Settings menu, navigate to Access Tokens.
  1. Enter a name for the token and optionally set an expiry date.
  2. Enable the following access scopes:
    • read_user
    • api
    • read_repository
    • write_repository
  3. Click Create Personal Access Token.
  4. Copy the token immediately, as it will not be visible again after this step.

Make sure to select a GitLab user which has "Maintainer" or "Owner" access to your org, or is a "Member" of all relevant repositories.

Store the token securely for future use.

5. Validate and Connect

  1. Paste the personal access token into the LinearB setup interface.
  2. LinearB will automatically validate the token.
  3. Once validated, proceed to repository selection.

For further assistance, visit our Support Page.

How did we do?

GitHub Enterprise Server (On-Prem) Connection Guide

Installing a GitHub Organization-Level Webhook

Contact