GitLab.com settings

These settings are used on GitLab.com, and are available to GitLab SaaS customers.

See some of these settings on the instance configuration page for GitLab.com.

Account and limit settings

GitLab.com uses these account limits. If a setting is not listed, the default value is the same as for GitLab Self-Managed instances:

If you are near or over the repository size limit, you can:

• Reduce your repository size with Git.
• Purchase additional storage.

Backups

See our backup strategy.

To back up an entire project on GitLab.com, you can export it:

• Through the UI.
• Through the API. You can also use the API to programmatically upload exports to a storage platform, such as Amazon S3.

With exports, be aware of what is and is not included in a project export.

To back up the Git repository of a project or wiki, clone it to another computer. All files uploaded to a wiki after August 22, 2020 are included when you clone a repository.

CI/CD

GitLab.com uses these GitLab CI/CD settings. Any settings or feature limits not listed here use the defaults listed in the related documentation:

Container registry

To use the GitLab container registry, Docker clients must have access to:

• The registry endpoint and GitLab.com for authorization.
• Google Cloud Storage or Google Cloud Content Delivery Network to download images.

GitLab.com is fronted by Cloudflare. For incoming connections to GitLab.com, you must allow CIDR blocks of Cloudflare (IPv4 and IPv6).

Email

Email configuration settings, IP addresses, and aliases.

Confirmation settings

GitLab.com uses these email confirmation settings:

• email_confirmation_setting is set to Hard.
• unconfirmed_users_delete_after_days is set to three days.

IP addresses

GitLab.com uses Mailgun to send emails from the mg.gitlab.com domain, and has its own dedicated IP addresses:

• 23.253.183.236
• 69.72.35.190
• 69.72.44.107
• 159.135.226.146
• 161.38.202.219
• 192.237.158.143
• 192.237.159.239
• 198.61.254.136
• 198.61.254.160
• 209.61.151.122

The IP addresses for mg.gitlab.com are subject to change at any time.

Service Desk alias

GitLab.com has a mailbox configured for Service Desk with the email address: contact-project+%{key}@incoming.gitlab.com. To use this mailbox, configure the custom suffix in project settings.

Gitaly RPC concurrency limits on GitLab.com

Per-repository Gitaly RPC concurrency and queuing limits are configured for different types of Git operations, like git clone. When these limits are exceeded, a fatal: remote error: GitLab is currently unable to handle this request due to load message is returned to the client.

For administrator documentation, see limit RPC concurrency.

GitLab Pages

Some settings for GitLab Pages differ from the defaults for GitLab Self-Managed:

The maximum size of your Pages site depends on the maximum artifact size, which is part of the GitLab CI/CD settings.

Rate limits also exist for GitLab Pages.

GitLab.com at scale

In addition to the GitLab Enterprise Edition Linux package install, GitLab.com uses the following applications and settings to achieve scale. All settings are publicly available, as Kubernetes configuration or Chef cookbooks.

Consul

Service discovery:

• gitlab-cookbooks / gitlab_consul · GitLab

Elastic cluster

We use Elasticsearch and Kibana for part of our monitoring solution:

• gitlab-cookbooks / gitlab-elk · GitLab
• gitlab-cookbooks / gitlab_elasticsearch · GitLab

Fluentd

We use Fluentd to unify our GitLab logs:

• gitlab-cookbooks / gitlab_fluentd · GitLab

Grafana

For the visualization of monitoring data:

• gitlab-cookbooks / gitlab-grafana · GitLab

HAProxy

High Performance TCP/HTTP Load Balancer:

• gitlab-cookbooks / gitlab-haproxy · GitLab

Prometheus

Prometheus complete our monitoring stack:

• gitlab-cookbooks / gitlab-prometheus · GitLab

Sentry

Open source error tracking:

• gitlab-cookbooks / gitlab-sentry · GitLab

GitLab-hosted runners

Use GitLab-hosted runners to run your CI/CD jobs on GitLab.com and GitLab Dedicated to seamlessly build, test, and deploy your application on different environments.

For more information, see GitLab-hosted runners.

Hostname list

Add these hostnames when you configure allow-lists in local HTTP(S) proxies, or other web-blocking software that governs end-user computers. Pages on GitLab.com load content from these hostnames:

• gitlab.com
• *.gitlab.com
• *.gitlab-static.net
• *.gitlab.io
• *.gitlab.net

Documentation and GitLab company pages served over docs.gitlab.com and about.gitlab.com also load certain page content directly from common public CDN hostnames.

Imports

GitLab.com uses settings to limit importing data into GitLab.

Default import sources

The import sources that are available to you by default depend on which GitLab you use:

• GitLab.com: All available import sources are enabled by default.
• GitLab Self-Managed: No import sources are enabled by default, and must be enabled.

Import placeholder user limits

Imports into GitLab.com limit the number of placeholder users for each top-level namespace. The limits differ depending on your plan and seat count. For more information, see the table of placeholder user limits for GitLab.com.

IP range

GitLab.com uses the IP ranges 34.74.90.64/28 and 34.74.226.0/24 for traffic from its Web/API fleet. This whole range is solely allocated to GitLab. Connections from webhooks or repository mirroring come from these IP addresses. You should allow these connections.

• Incoming connections - GitLab.com is fronted by Cloudflare. For incoming connections to GitLab.com, allow CIDR blocks of Cloudflare (IPv4 and IPv6).

• Outgoing connections from CI/CD runners - We don’t provide static IP addresses for outgoing connections from CI/CD runners. However, these guidelines can help:

  • Linux GPU-enabled and Linux Arm64 runners are deployed into Google Cloud, in us-central1.
  • Other GitLab.com instance runners are deployed into Google Cloud in us-east1.
  • macOS runners are hosted on AWS in the us-east-1 region, with runner managers hosted on Google Cloud.

To configure an IP-based firewall, you must allow both AWS IP address ranges and Google Cloud IP address ranges.

See how to look up IP address ranges or CIDR blocks for GCP.

Logs on GitLab.com

Fluentd parses our logs, then sends them to:

• Stackdriver Logging, which stores logs long-term in Google Cold Storage (GCS).
• Cloud Pub/Sub, which forwards logs to an Elastic cluster using pubsubbeat.

For more information, see our runbooks:

• A detailed list of what we’re logging
• Our current log retention policies
• A diagram of our logging infrastructure

Job logs

By default, GitLab does not expire job logs. Job logs are retained indefinitely, and can’t be configured on GitLab.com to expire. You can erase job logs manually with the Jobs API or by deleting a pipeline

Maximum number of reviewers and assignees

Merge requests enforce these maximums:

• Maximum assignees: 200
• Maximum reviewers: 200

Merge request limits

GitLab limits each merge request to 1000 diff versions. Merge requests that reach this limit cannot be updated further. Instead, close the affected merge request and create a new merge request.

Password requirements

GitLab.com sets these requirements for passwords on new accounts and password changes:

• Minimum character length 8 characters.
• Maximum character length 128 characters.
• All characters are accepted. For example, ~, !, @, #, $, %, ^, &, *, (), [], _, +, =, and -.

Project and group deletion

Settings related to the deletion of projects and groups.

Delayed group deletion

Groups in GitLab Premium and GitLab Ultimate have delayed deletion enabled by default. Groups are permanently deleted after a seven-day delay.

If you are on GitLab Free, your groups are immediately deleted, and you cannot restore them.

See how to view and restore groups marked for deletion.

Delayed project deletion

In GitLab Premium and GitLab Ultimate, projects are permanently deleted after a seven-day delay.

If you are on GitLab Free, your projects are immediately deleted, and you cannot restore them.

See how to view and restore projects marked for deletion.

Inactive project deletion

Inactive project deletion is disabled on GitLab.com.

Package registry limits

The maximum file size for a package uploaded to the GitLab package registry varies by format:

Puma

GitLab.com uses the default of 60 seconds for Puma request timeouts.

Rate limits on GitLab.com

When a request is rate limited, GitLab responds with a 429 status code. The client should wait before attempting the request again. There are also informational headers with this response detailed in rate limiting responses.

The following table describes the rate limits for GitLab.com:

More details are available on the rate limits for protected paths and raw endpoints.

GitLab can rate-limit requests at several layers. The rate limits listed here are configured in the application. These limits are the most restrictive for each IP address. For more information about the rate limits for GitLab.com, see the documentation in the handbook.

Group and project import by uploading export files

To help avoid abuse, GitLab.com uses rate limits:

• Project and group imports.
• Group and project exports that use files.
• Export downloads.

For more information, see:

• Project import/export rate limits.
• Group import/export rate limits.

IP blocks

IP blocks can occur when GitLab.com receives unusual traffic from a single IP address that the system views as potentially malicious. This can be based on rate limit settings. After the unusual traffic ceases, the IP address is automatically released depending on the type of block, as described in a following section.

If you receive a 403 Forbidden error for all requests to GitLab.com, check for any automated processes that may be triggering a block. For assistance, contact GitLab Support with details, such as the affected IP address.

Git and container registry failed authentication ban

GitLab.com responds with HTTP status code 403 for 15 minutes when a single IP address sends 300 failed authentication requests in a 1-minute period.

This applies only to Git requests and container registry (/jwt/auth) requests (combined).

This limit:

• Is reset by requests that authenticate successfully. For example, 299 failed authentication requests followed by 1 successful request, followed by 299 more failed authentication requests, does not trigger a ban.
• Does not apply to JWT requests authenticated by gitlab-ci-token.

No response headers are provided.

git requests over https always send an unauthenticated request first, which for private repositories results in a 401 error. git then attempts an authenticated request with a username, password, or access token (if available). These requests might lead to a temporary IP block if too many requests are sent simultaneously. To resolve this issue, use SSH keys to communicate with GitLab.

Non-configurable limits

For more information about non-configurable rate limits used on GitLab.com, see non-configurable limits

Pagination response headers

For performance reasons, if a query returns more than 10,000 records, GitLab excludes some headers.

Protected paths throttle

If the same IP address sends more than 10 POST requests in a minute to protected paths, GitLab.com returns a 429 HTTP status code.

See the source below for which paths are protected. They include user creation, user confirmation, user sign in, and password reset.

User and IP rate limits includes a list of the headers responded to blocked requests.

See Protected Paths for more details.

Rate limiting responses

For information on rate limiting responses, see:

• List of headers on responses to blocked requests.
• Customizable response text.

SSH maximum number of connections

GitLab.com defines the maximum number of concurrent, unauthenticated SSH connections by using the MaxStartups setting. If more than the maximum number of allowed connections occur concurrently, they are dropped and users get an ssh_exchange_identification error.

Visibility settings

Projects, groups, and snippets have the Internal visibility setting disabled on GitLab.com.

Sidekiq

GitLab.com runs Sidekiq as an external process for Ruby job scheduling.

The current settings are in the GitLab.com Kubernetes pod configuration.

SSH keys and authentication

Settings related to authentication with SSH. For information about maximum connections, see SSH maximum number of connections.

Alternative SSH port

GitLab.com can be reached by using a different SSH port for git+ssh.

An example ~/.ssh/config is the following:

Host gitlab.com
  Hostname altssh.gitlab.com
  User git
  Port 443
  PreferredAuthentications publickey
  IdentityFile ~/.ssh/gitlab

SSH host keys fingerprints

Go to the current instance configuration to see the SSH host key fingerprints on GitLab.com.

1. Sign in to GitLab.
2. On the left sidebar, select Help ( ) > Help.
3. On the Help page, select Check the current instance configuration.

In the instance configuration, you see the SSH host key fingerprints:

The first time you connect to a GitLab.com repository, one of these keys is displayed in the output.

SSH key restrictions

GitLab.com uses the default SSH key restrictions.

SSH known_hosts entries

To skip manual fingerprint confirmation in SSH, add the following to .ssh/known_hosts:

gitlab.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAfuCHKVTjquxvt6CM6tdG4SLp1Btn/nOeHHE5UOzRdf
gitlab.com ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCsj2bNKTBSpIYDEGk9KxsGh3mySTRgMtXL583qmBpzeQ+jqCMRgBqB98u3z++J1sKlXHWfM9dyhSevkMwSbhoR8XIq/U0tCNyokEi/ueaBMCvbcTHhO7FcwzY92WK4Yt0aGROY5qX2UKSeOvuP4D6TPqKF1onrSzH9bx9XUf2lEdWT/ia1NEKjunUqu1xOB/StKDHMoX4/OKyIzuS0q/T1zOATthvasJFoPrAjkohTyaDUz2LN5JoH839hViyEG82yB+MjcFV5MU3N1l1QL3cVUCh93xSaua1N85qivl+siMkPGbO5xR/En4iEY6K2XPASUEMaieWVNTRCtJ4S8H+9
gitlab.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBFSMqzJeV9rUzU4kWitGjeR4PWSa29SPqJ1fVkhtj3Hw9xjLVXVYrU9QlYWrOLXBpQ6KWjbjTDTdDkoohFzgbEY=

Webhooks

The following limits apply for webhooks.

Rate limits

For each top-level namespace, the number of times each minute that a webhook can be called. The limit varies depending on your plan and the number of seats in your subscription.

Other limits

For GitLab Self-Managed instance limits, see:

• Webhook rate limit.
• Number of webhooks.
• Webhook timeout.
• Parallel Pages deployments..