url stringlengths 24 122 | repo_url stringlengths 60 156 | date_extracted stringdate 2025-08-13 00:00:00 2025-08-13 00:00:00 | root stringlengths 3 85 | breadcrumbs listlengths 1 6 | filename stringlengths 6 60 | stage stringclasses 33
values | group stringclasses 81
values | info stringclasses 22
values | title stringlengths 3 110 ⌀ | description stringlengths 11 359 ⌀ | clean_text stringlengths 47 3.32M | rich_text stringlengths 321 3.32M |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
https://docs.gitlab.com/administration/geo/disaster_recovery | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/_index.md | 2025-08-13 | doc/administration/geo/disaster_recovery | [
"doc",
"administration",
"geo",
"disaster_recovery"
] | _index.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Disaster Recovery (Geo) | Recover from a disaster, using a Geo instance. |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
Geo replicates your database, your Git repositories, and other assets.
Some [known issues](../_index.md#known-issues) exist.
{{< alert type="warning" >}}
Multi-secondary configurations require the complete re-synchronizati... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Disaster Recovery (Geo)
description: Recover from a disaster, using a Geo instance.
breadcrumbs:
-... |
https://docs.gitlab.com/administration/geo/bring_primary_back | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/bring_primary_back.md | 2025-08-13 | doc/administration/geo/disaster_recovery | [
"doc",
"administration",
"geo",
"disaster_recovery"
] | bring_primary_back.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Bring a demoted primary site back online | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
After a failover, it is possible to fail back to the demoted **primary** site to
restore your original configuration. This process consists of two steps:
1. Making the old **primary** site a **secondary** site.
1. Promoting... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Bring a demoted primary site back online
breadcrumbs:
- doc
- administration
- geo
- disaster_reco... |
https://docs.gitlab.com/administration/geo/disaster_recovery/planned_failover_single_node | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/disaster_recovery/planned_failover_single_node.md | 2025-08-13 | doc/administration/geo/disaster_recovery/runbooks | [
"doc",
"administration",
"geo",
"disaster_recovery",
"runbooks"
] | planned_failover_single_node.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Disaster Recovery (Geo) promotion runbooks | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
- Status: Experiment
{{< /details >}}
Disaster Recovery (Geo) promotion runbooks.
{{< alert type="warning" >}}
This runbook is an [experiment](../../../../policy/development_stages_support.md#experiment). For complete, production-ready doc... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
ignore_in_report: true
title: Disaster Recovery (Geo) promotion runbooks
breadcrumbs:
- doc
- administrat... |
https://docs.gitlab.com/administration/geo/disaster_recovery/planned_failover_multi_node | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/disaster_recovery/planned_failover_multi_node.md | 2025-08-13 | doc/administration/geo/disaster_recovery/runbooks | [
"doc",
"administration",
"geo",
"disaster_recovery",
"runbooks"
] | planned_failover_multi_node.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Disaster Recovery (Geo) promotion runbooks | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
- Status: Experiment
{{< /details >}}
Disaster Recovery (Geo) promotion runbooks.
{{< alert type="warning" >}}
This runbook is an [experiment](../../../../policy/development_stages_support.md#experiment). For complete, production-ready doc... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
ignore_in_report: true
title: Disaster Recovery (Geo) promotion runbooks
breadcrumbs:
- doc
- administrat... |
https://docs.gitlab.com/administration/geo/faq | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/faq.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | faq.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Geo Frequently Asked Questions | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
## What are the minimum requirements to run Geo?
The requirements are listed [on the index page](../_index.md#requirements-for-running-geo)
## How does Geo know which projects to sync?
On each **secondary** site, there is... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
gitlab_dedicated: false
title: Geo Frequently Asked Questions
breadcrumbs:
- doc
- administration
- geo
-... |
https://docs.gitlab.com/administration/geo/upgrading_the_geo_sites | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/upgrading_the_geo_sites.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | upgrading_the_geo_sites.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Upgrading the Geo sites | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
{{< alert type="warning" >}}
Read these sections carefully before updating your Geo sites. Not following
version-specific upgrade steps may result in unexpected downtime. If you have
any specific questions, [contact Support... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Upgrading the Geo sites
breadcrumbs:
- doc
- administration
- geo
- replication
---
{{< details ... |
https://docs.gitlab.com/administration/geo/remove_geo_site | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/remove_geo_site.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | remove_geo_site.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Removing secondary Geo sites | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
**Secondary** sites can be removed from the Geo cluster using the Geo administration page of the **primary** site. To remove a **secondary** site:
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > N... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Removing secondary Geo sites
breadcrumbs:
- doc
- administration
- geo
- replication
---
{{< det... |
https://docs.gitlab.com/administration/geo/geo_validation_tests | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/geo_validation_tests.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | geo_validation_tests.md | null | null | null | null | null |
<!-- markdownlint-disable -->
This document was moved to [another location](../../../development/geo/geo_validation_tests.md).
<!-- This redirect file can be deleted after 2025-11-03. -->
<!-- Redirects that point to other docs in the same project expire in three months. -->
<!-- Redirects that point to docs in a d... | ---
redirect_to: ../../../development/geo/geo_validation_tests.md
remove_date: '2025-11-03'
breadcrumbs:
- doc
- administration
- geo
- replication
---
<!-- markdownlint-disable -->
This document was moved to [another location](../../../development/geo/geo_validation_tests.md).
<!-- This redirect file can be delete... |
https://docs.gitlab.com/administration/geo/datatypes | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/datatypes.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | datatypes.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Supported Geo data types | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
A Geo data type is a specific class of data that is required by one or more GitLab features to
store relevant information.
To replicate data produced by these features with Geo, we use several strategies to access, transfer... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
gitlab_dedicated: false
title: Supported Geo data types
breadcrumbs:
- doc
- administration
- geo
- repli... |
https://docs.gitlab.com/administration/geo/configuration | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/configuration.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | configuration.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Configure a new **secondary** site | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
{{< alert type="note" >}}
This is the final step in setting up a **secondary** Geo site. Stages of the
setup process must be completed in the documented order.
If not, [complete all prior stages](../setup/_index.md#using-li... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Configure a new **secondary** site
breadcrumbs:
- doc
- administration
- geo
- replication
---
{... |
https://docs.gitlab.com/administration/geo/single_sign_on | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/single_sign_on.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | single_sign_on.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Geo with Single Sign On (SSO) | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This documentation only discusses Geo-specific SSO considerations and configuration. For more information on general authentication, see [GitLab authentication and authorization](../../auth/_index.md).
## Configuring instan... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Geo with Single Sign On (SSO)
breadcrumbs:
- doc
- administration
- geo
- replication
---
{{< de... |
https://docs.gitlab.com/administration/geo/security_review | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/security_review.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | security_review.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Geo security review (Q&A) | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
The following security review of the Geo feature set focuses on security aspects of
the feature as they apply to customers running their own GitLab instances. The review
questions are based in part on the [OWASP Application ... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Geo security review (Q&A)
breadcrumbs:
- doc
- administration
- geo
- replication
---
{{< detail... |
https://docs.gitlab.com/administration/geo/object_storage | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/object_storage.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | object_storage.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Geo with Object storage | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
{{< history >}}
- Verification of files stored in object storage was [introduced](https://gitlab.com/groups/gitlab-org/-/epics/8056) in GitLab 16.4 [with a flag](../../feature_flags/_index.md) named `geo_object_storage_veri... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
gitlab_dedicated: false
title: Geo with Object storage
breadcrumbs:
- doc
- administration
- geo
- replic... |
https://docs.gitlab.com/administration/geo/location_aware_git_url | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/location_aware_git_url.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | location_aware_git_url.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Location-aware Git remote URL with AWS Route53 | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
{{< alert type="note" >}}
[GitLab Geo supports location-aware DNS including web UI and API traffic.](../secondary_proxy/_index.md#configure-location-aware-dns)
This configuration is recommended over the location-aware Git r... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Location-aware Git remote URL with AWS Route53
breadcrumbs:
- doc
- administration
- geo
- replica... |
https://docs.gitlab.com/administration/geo/tuning | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/tuning.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | tuning.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Tuning Geo | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
You can limit the number of concurrent operations the sites can run
in the background.
## Changing the sync/verification concurrency values
On the **primary** site:
1. On the left sidebar, at the bottom, select **Admin**.... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
gitlab_dedicated: false
title: Tuning Geo
breadcrumbs:
- doc
- administration
- geo
- replication
---
{... |
https://docs.gitlab.com/administration/geo/usage | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/usage.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | usage.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Using a Geo Site | null |
<!-- Please update EE::GitLab::GeoGitAccess::GEO_SERVER_DOCS_URL if this file is moved) -->
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
After you set up the [database replication and configure the Geo nodes](../setup/_index.md), use your closest GitLab site as you wo... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Using a Geo Site
breadcrumbs:
- doc
- administration
- geo
- replication
---
<!-- Please update ... |
https://docs.gitlab.com/administration/geo/multiple_servers | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/multiple_servers.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | multiple_servers.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Geo for multiple nodes | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This document describes a minimal reference architecture for running Geo
in a multi-node configuration. If your multi-node setup differs from the one
described, it is possible to adapt these instructions to your needs.
This... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Geo for multiple nodes
breadcrumbs:
- doc
- administration
- geo
- replication
---
{{< details >... |
https://docs.gitlab.com/administration/geo/disable_geo | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/disable_geo.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | disable_geo.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Disabling Geo | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
If you want to revert to a regular Linux package installation setup after a test, or you have encountered a Disaster Recovery
situation and you want to disable Geo momentarily, you can use these instructions to disable your
... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Disabling Geo
breadcrumbs:
- doc
- administration
- geo
- replication
---
{{< details >}}
- Tie... |
https://docs.gitlab.com/administration/geo/pause_resume_replication | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/pause_resume_replication.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | pause_resume_replication.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Pausing and resuming replication | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
{{< alert type="warning" >}}
Pausing and resuming of replication is only supported for Geo installations using a
Linux package-managed database. External databases are not supported.
**Do not pause replication** if the pri... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Pausing and resuming replication
breadcrumbs:
- doc
- administration
- geo
- replication
---
{{<... |
https://docs.gitlab.com/administration/geo/container_registry | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/container_registry.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | container_registry.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Container registry for a secondary site | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
You can set up a container registry on your **secondary** Geo site that mirrors the one on the **primary** Geo site. This container registry replication is used only for disaster recovery purposes.
Do not push to the contai... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Container registry for a secondary site
breadcrumbs:
- doc
- administration
- geo
- replication
--... |
https://docs.gitlab.com/administration/geo/selective_synchronization | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/selective_synchronization.md | 2025-08-13 | doc/administration/geo/replication | [
"doc",
"administration",
"geo",
"replication"
] | selective_synchronization.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Selective synchronization | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
Geo supports selective synchronization, which allows administrators to choose
which projects should be synchronized by **secondary** sites.
A subset of projects can be chosen, either by group or by storage shard. The
former ... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Selective synchronization
breadcrumbs:
- doc
- administration
- geo
- replication
---
{{< detail... |
https://docs.gitlab.com/administration/geo/replication/common | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/replication/common.md | 2025-08-13 | doc/administration/geo/replication/troubleshooting | [
"doc",
"administration",
"geo",
"replication",
"troubleshooting"
] | common.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting common Geo errors | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
## Basic troubleshooting
Before attempting more advanced troubleshooting:
- Check [the health of the Geo sites](#check-the-health-of-the-geo-sites).
- Check [if PostgreSQL replication is working](#check-if-postgresql-repli... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting common Geo errors
breadcrumbs:
- doc
- administration
- geo
- replication
- troubl... |
https://docs.gitlab.com/administration/geo/replication/failover | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/replication/failover.md | 2025-08-13 | doc/administration/geo/replication/troubleshooting | [
"doc",
"administration",
"geo",
"replication",
"troubleshooting"
] | failover.md | null | null | null | null | null |
<!-- markdownlint-disable -->
<!-- vale off -->
This document was moved to [another location](../../disaster_recovery/failover_troubleshooting.md).
<!-- This redirect file can be deleted after <2025-08-02>. -->
<!-- Redirects that point to other docs in the same project expire in three months. -->
<!-- Redirects th... | ---
redirect_to: ../../disaster_recovery/failover_troubleshooting.md
remove_date: '2025-08-02'
breadcrumbs:
- doc
- administration
- geo
- replication
- troubleshooting
---
<!-- markdownlint-disable -->
<!-- vale off -->
This document was moved to [another location](../../disaster_recovery/failover_troubleshooting.m... |
https://docs.gitlab.com/administration/geo/replication/client_http | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/replication/client_http.md | 2025-08-13 | doc/administration/geo/replication/troubleshooting | [
"doc",
"administration",
"geo",
"replication",
"troubleshooting"
] | client_http.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting Geo client and HTTP response code errors | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
## Fixing client errors
### Authorization errors from LFS HTTP(S) client requests
You may have problems if you're running a version of [Git LFS](https://git-lfs.com/) before 2.4.2.
As noted in [this authentication issue](h... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting Geo client and HTTP response code errors
breadcrumbs:
- doc
- administration
- geo... |
https://docs.gitlab.com/administration/geo/replication/synchronization_verification | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/replication/synchronization_verification.md | 2025-08-13 | doc/administration/geo/replication/troubleshooting | [
"doc",
"administration",
"geo",
"replication",
"troubleshooting"
] | synchronization_verification.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting Geo synchronization and verification errors | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
If you notice replication or verification failures in `Admin > Geo > Sites` or the [Sync status Rake task](common.md#sync-status-rake-task), you can try to resolve the failures with the following general steps:
1. Geo autom... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting Geo synchronization and verification errors
breadcrumbs:
- doc
- administration
- ... |
https://docs.gitlab.com/administration/geo/replication/troubleshooting | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/replication/_index.md | 2025-08-13 | doc/administration/geo/replication/troubleshooting | [
"doc",
"administration",
"geo",
"replication",
"troubleshooting"
] | _index.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting Geo | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
When working with Geo, you might encounter the following issues:
- Basic troubleshooting and [common errors](common.md)
- [Client and HTTP response code errors](client_http.md)
- [PostgreSQL replication errors](postgresql_r... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting Geo
breadcrumbs:
- doc
- administration
- geo
- replication
- troubleshooting
---
... |
https://docs.gitlab.com/administration/geo/replication/postgresql_replication | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/replication/postgresql_replication.md | 2025-08-13 | doc/administration/geo/replication/troubleshooting | [
"doc",
"administration",
"geo",
"replication",
"troubleshooting"
] | postgresql_replication.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting Geo PostgreSQL replication | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
The following sections outline troubleshooting steps for fixing replication error messages (indicated by `Database replication working? ... no` in the
[`geo:check` output](common.md#health-check-rake-task).
The instructions ... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting Geo PostgreSQL replication
breadcrumbs:
- doc
- administration
- geo
- replication... |
https://docs.gitlab.com/administration/geo/runners | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/runners.md | 2025-08-13 | doc/administration/geo/secondary_proxy | [
"doc",
"administration",
"geo",
"secondary_proxy"
] | runners.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Secondary runners | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/9779) in GitLab 16.8 [with a flag](../../feature_flags/_index.md) named `geo_proxy_check_pipeline_refs`. Disabled by default.
- [... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
gitlab_dedicated: true
title: Secondary runners
breadcrumbs:
- doc
- administration
- geo
- secondary_pro... |
https://docs.gitlab.com/administration/geo/secondary_proxy | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/geo/_index.md | 2025-08-13 | doc/administration/geo/secondary_proxy | [
"doc",
"administration",
"geo",
"secondary_proxy"
] | _index.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Geo proxying for secondary sites | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
{{< history >}}
- HTTP proxying for secondary sites with separate URLs [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/346112) in GitLab 14.5 [with a flag](../../feature_flags/_index.md) named `geo_secondary_prox... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Geo proxying for secondary sites
breadcrumbs:
- doc
- administration
- geo
- secondary_proxy
---
... |
https://docs.gitlab.com/administration/fast_ssh_key_lookup | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/fast_ssh_key_lookup.md | 2025-08-13 | doc/administration/operations | [
"doc",
"administration",
"operations"
] | fast_ssh_key_lookup.md | Create | Source Code | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Fast lookup of SSH keys | Configure a faster SSH authorization method for GitLab instances with many users. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
When the number of users grows, SSH operations become slow because OpenSSH performs a
linear search through the `authorized_keys` file to authenticate users.
This process requires significant time and disk I/O, which d... | ---
stage: Create
group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
gitlab_dedicated: false
description: Configure a faster SSH authorization method for GitLab instances w... |
https://docs.gitlab.com/administration/moving_repositories | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/moving_repositories.md | 2025-08-13 | doc/administration/operations | [
"doc",
"administration",
"operations"
] | moving_repositories.md | Data Access | Gitaly | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Moving repositories managed by GitLab | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
You can move all repositories managed by GitLab to another file system or another server.
## Moving data in a GitLab instance
The GitLab API is the recommended way to move Git repositories:
- Between servers.
- Betw... | ---
stage: Data Access
group: Gitaly
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Moving repositories managed by GitLab
breadcrumbs:
- doc
- administration
- operations
---
{{<... |
https://docs.gitlab.com/administration/puma | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/puma.md | 2025-08-13 | doc/administration/operations | [
"doc",
"administration",
"operations"
] | puma.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Configure the bundled Puma instance of the GitLab package | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
Puma is a fast, multi-threaded, and highly concurrent HTTP 1.1 server for
Ruby applications. It runs the core Rails application that provides the user-facing
features of GitLab.
## Reducing memory use
To reduce memor... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Configure the bundled Puma instance of the GitLab package
breadcrumbs:
- doc
- adminis... |
https://docs.gitlab.com/administration/rails_console | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/rails_console.md | 2025-08-13 | doc/administration/operations | [
"doc",
"administration",
"operations"
] | rails_console.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Rails console | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
At the heart of GitLab is a web application
[built using the Ruby on Rails framework](https://about.gitlab.com/blog/2018/10/29/why-we-use-rails-to-build-gitlab/).
The [Rails console](https://guides.rubyonrails.org/comm... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Rails console
breadcrumbs:
- doc
- administration
- operations
---
{{< details >}}
... |
https://docs.gitlab.com/administration/gitlab_sshd | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/gitlab_sshd.md | 2025-08-13 | doc/administration/operations | [
"doc",
"administration",
"operations"
] | gitlab_sshd.md | Create | Source Code | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | `gitlab-sshd` | Configure `gitlab-sshd`, a lightweight alternative to OpenSSH, for your GitLab instance. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
`gitlab-sshd` is [a standalone SSH server](https://gitlab.com/gitlab-org/gitlab-shell/-/tree/main/internal/sshd)
written in Go. It is a lightweight alternative to OpenSSH. It is part of the `gitlab-shell` package and
h... | ---
stage: Create
group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Configure `gitlab-sshd`, a lightweight alternative to OpenSSH, for your
GitLab instance.... |
https://docs.gitlab.com/administration/ssh_certificates | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/ssh_certificates.md | 2025-08-13 | doc/administration/operations | [
"doc",
"administration",
"operations"
] | ssh_certificates.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | User lookup via OpenSSH's AuthorizedPrincipalsCommand | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
The default SSH authentication for GitLab requires users to upload their SSH
public keys before they can use the SSH transport.
In centralized (for example, corporate) environments this can be a hassle
operationally, ... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: User lookup via OpenSSH's AuthorizedPrincipalsCommand
breadcrumbs:
- doc
- administrat... |
https://docs.gitlab.com/administration/operations | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/_index.md | 2025-08-13 | doc/administration/operations | [
"doc",
"administration",
"operations"
] | _index.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Maintain GitLab | Backup and restore, move repos, maintenance tasks. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
Keep your GitLab instance up and running.
- [Housekeeping](../housekeeping.md)
- [Activate GitLab EE with license](../license_file.md)
- [Fast SSH key lookup](fast_ssh_key_lookup.md)
- [File system benchmarking](files... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Backup and restore, move repos, maintenance tasks.
title: Maintain GitLab
breadc... |
https://docs.gitlab.com/administration/filesystem_benchmarking | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/filesystem_benchmarking.md | 2025-08-13 | doc/administration/operations | [
"doc",
"administration",
"operations"
] | filesystem_benchmarking.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | File system performance benchmarking | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
File system performance has a big impact on overall GitLab performance,
especially for actions that read or write to Git repositories. This information
helps benchmark file system performance against known good and bad... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: File system performance benchmarking
breadcrumbs:
- doc
- administration
- operations
... |
https://docs.gitlab.com/administration/omnibus_packages | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/omnibus_packages.md | 2025-08-13 | doc/administration/package_information | [
"doc",
"administration",
"package_information"
] | omnibus_packages.md | GitLab Delivery | Build | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Packages and images from the Linux package | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
Below you can find some basic information on why GitLab provides packages and
a Docker image that come with bundled dependencies.
These methods are great for physical and virtual machine installations, and simple Dock... | ---
stage: GitLab Delivery
group: Build
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Packages and images from the Linux package
breadcrumbs:
- doc
- administration
- package_info... |
https://docs.gitlab.com/administration/defaults | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/defaults.md | 2025-08-13 | doc/administration/package_information | [
"doc",
"administration",
"package_information"
] | defaults.md | GitLab Delivery | Build | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Package defaults | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
Unless configuration is specified in the `/etc/gitlab/gitlab.rb` file,
the package assumes the defaults as noted below.
## Ports
See the table below for the list of ports that the Linux package assigns by default:
|... | ---
stage: GitLab Delivery
group: Build
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Package defaults
breadcrumbs:
- doc
- administration
- package_information
---
{{< details ... |
https://docs.gitlab.com/administration/postgresql_versions | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/postgresql_versions.md | 2025-08-13 | doc/administration/package_information | [
"doc",
"administration",
"package_information"
] | postgresql_versions.md | GitLab Delivery | Build | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | PostgreSQL versions shipped with the Linux package | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
{{< alert type="note" >}}
This table lists only GitLab versions where a significant change happened in the
package regarding PostgreSQL versions, not all.
{{< /alert >}}
Usually, PostgreSQL versions change with majo... | ---
stage: GitLab Delivery
group: Build
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: PostgreSQL versions shipped with the Linux package
breadcrumbs:
- doc
- administration
- pack... |
https://docs.gitlab.com/administration/supported_os | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/supported_os.md | 2025-08-13 | doc/administration/package_information | [
"doc",
"administration",
"package_information"
] | supported_os.md | null | null | null | null | null |
<!-- markdownlint-disable -->
This document was moved to [another location](../../install/package/_index.md).
<!-- This redirect file can be deleted after <2025-09-02>. -->
<!-- Redirects that point to other docs in the same project expire in three months. -->
<!-- Redirects that point to docs in a different projec... | ---
redirect_to: ../../install/package/_index.md
remove_date: '2025-09-02'
breadcrumbs:
- doc
- administration
- package_information
---
<!-- markdownlint-disable -->
This document was moved to [another location](../../install/package/_index.md).
<!-- This redirect file can be deleted after <2025-09-02>. -->
<!-- R... |
https://docs.gitlab.com/administration/signed_packages | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/signed_packages.md | 2025-08-13 | doc/administration/package_information | [
"doc",
"administration",
"package_information"
] | signed_packages.md | GitLab Delivery | Build | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Package Signatures | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
<!-- vale gitlab_base.SubstitutionWarning = NO -->
Linux packages produced by GitLab are created using [Omnibus](https://github.com/chef/omnibus), for which GitLab
has added DEB signing using `debsigs` in [our own for... | ---
stage: GitLab Delivery
group: Build
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Package Signatures
breadcrumbs:
- doc
- administration
- package_information
---
{{< detail... |
https://docs.gitlab.com/administration/package_information | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/_index.md | 2025-08-13 | doc/administration/package_information | [
"doc",
"administration",
"package_information"
] | _index.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Package information | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
The Linux package is bundled with all dependencies required for GitLab
to function correctly. More details can be found
at [bundling dependencies document](omnibus_packages.md).
## Package Version
The released packag... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Package information
breadcrumbs:
- doc
- administration
- package_information
---
{{... |
https://docs.gitlab.com/administration/deprecation_policy | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/deprecation_policy.md | 2025-08-13 | doc/administration/package_information | [
"doc",
"administration",
"package_information"
] | deprecation_policy.md | GitLab Delivery | Build | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Linux package deprecation policy | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
The Linux packages come with number of different libraries and services which offers users plethora of configuration options.
As libraries and services get updated, their configuration options change
and become obsole... | ---
stage: GitLab Delivery
group: Build
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Linux package deprecation policy
breadcrumbs:
- doc
- administration
- package_information
--... |
https://docs.gitlab.com/administration/licensing | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/licensing.md | 2025-08-13 | doc/administration/package_information | [
"doc",
"administration",
"package_information"
] | licensing.md | GitLab Delivery | Build | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Package Licensing | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
## License
While GitLab itself is MIT, the Linux package sources are licensed under the Apache-2.0.
## License file location
Starting with version 8.11, the Linux package contains license
information of all software... | ---
stage: GitLab Delivery
group: Build
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Package Licensing
breadcrumbs:
- doc
- administration
- package_information
---
{{< details... |
https://docs.gitlab.com/administration/pages | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/_index.md | 2025-08-13 | doc/administration/pages | [
"doc",
"administration",
"pages"
] | _index.md | Plan | Knowledge | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | GitLab Pages administration | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
GitLab Pages provides static site hosting for GitLab projects and groups.
Server administrators must configure Pages before users can access this feature.
With GitLab Pages, administrators:
- Host static websites secu... | ---
stage: Plan
group: Knowledge
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: GitLab Pages administration
breadcrumbs:
- doc
- administration
- pages
---
{{< details >}}
- Tie... |
https://docs.gitlab.com/administration/source | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/source.md | 2025-08-13 | doc/administration/pages | [
"doc",
"administration",
"pages"
] | source.md | Plan | Knowledge | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | GitLab Pages administration for self-compiled installations | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
{{< alert type="note" >}}
Before attempting to enable GitLab Pages, first make sure you have
[installed GitLab](../../install/self_compiled/_index.md) successfully.
{{< /alert >}}
This document explains how to confi... | ---
stage: Plan
group: Knowledge
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: GitLab Pages administration for self-compiled installations
breadcrumbs:
- doc
- administration
- pa... |
https://docs.gitlab.com/administration/troubleshooting | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/troubleshooting.md | 2025-08-13 | doc/administration/pages | [
"doc",
"administration",
"pages"
] | troubleshooting.md | Plan | Knowledge | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting GitLab Pages administration | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This page contains a list of issues you might encounter when administering GitLab Pages.
## How to see GitLab Pages logs
You can see Pages daemon logs by running:
```shell
sudo gitlab-ctl tail gitlab-pages
```
You ... | ---
stage: Plan
group: Knowledge
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting GitLab Pages administration
breadcrumbs:
- doc
- administration
- pages
---
{{< de... |
https://docs.gitlab.com/administration/postgresql | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/postgresql.md | 2025-08-13 | doc/administration/troubleshooting | [
"doc",
"administration",
"troubleshooting"
] | postgresql.md | Data Access | Database Operations | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | PostgreSQL | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This page contains information about PostgreSQL the GitLab Support team uses
when troubleshooting. GitLab makes this information public, so that anyone can
make use of the Support team's collected knowledge.
{{< alert... | ---
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: PostgreSQL
breadcrumbs:
- doc
- administration
- troubleshooting
---
{{< details ... |
https://docs.gitlab.com/administration/troubleshooting | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/_index.md | 2025-08-13 | doc/administration/troubleshooting | [
"doc",
"administration",
"troubleshooting"
] | _index.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting a GitLab installation | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This page documents a collection of resources to help you troubleshoot a GitLab
installation.
This list is not necessarily comprehensive. If you don't find what you're looking
for in this list, you should search the d... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting a GitLab installation
breadcrumbs:
- doc
- administration
- troublesho... |
https://docs.gitlab.com/administration/gitlab_rails_cheat_sheet | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/gitlab_rails_cheat_sheet.md | 2025-08-13 | doc/administration/troubleshooting | [
"doc",
"administration",
"troubleshooting"
] | gitlab_rails_cheat_sheet.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | GitLab Rails Console Cheat Sheet | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This was the GitLab Support Team's collection of information regarding the GitLab Rails
console, for use while troubleshooting. It is listed here for posterity,
as most content has been moved to feature-specific troubl... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: GitLab Rails Console Cheat Sheet
breadcrumbs:
- doc
- administration
- troubleshooting... |
https://docs.gitlab.com/administration/diagnostics_tools | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/diagnostics_tools.md | 2025-08-13 | doc/administration/troubleshooting | [
"doc",
"administration",
"troubleshooting"
] | diagnostics_tools.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Diagnostics tools | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
These are some of the diagnostics tools the GitLab Support team uses during troubleshooting.
They are listed here for transparency, and for users with experience
with troubleshooting GitLab. If you are currently having... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Diagnostics tools
breadcrumbs:
- doc
- administration
- troubleshooting
---
{{< deta... |
https://docs.gitlab.com/administration/linux_cheat_sheet | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/linux_cheat_sheet.md | 2025-08-13 | doc/administration/troubleshooting | [
"doc",
"administration",
"troubleshooting"
] | linux_cheat_sheet.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Linux cheat sheet | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This is the GitLab Support Team's collection of information regarding Linux, that they
sometimes use while troubleshooting. It is listed here for transparency,
and for users with experience with Linux. If you are curre... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Linux cheat sheet
breadcrumbs:
- doc
- administration
- troubleshooting
---
{{< deta... |
https://docs.gitlab.com/administration/test_environments | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/test_environments.md | 2025-08-13 | doc/administration/troubleshooting | [
"doc",
"administration",
"troubleshooting"
] | test_environments.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Apps for a testing environment | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This is the GitLab Support Team's collection of information regarding testing environments,
for use while troubleshooting. It is listed here for transparency, and it may be useful
for users with experience with these t... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Apps for a testing environment
breadcrumbs:
- doc
- administration
- troubleshooting
-... |
https://docs.gitlab.com/administration/3k_users | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/3k_users.md | 2025-08-13 | doc/administration/reference_architectures | [
"doc",
"administration",
"reference_architectures"
] | 3k_users.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Reference architecture: Up to 60 RPS or 3,000 users | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This page describes the GitLab reference architecture designed to target a peak load of 60 requests per second (RPS), the typical peak load of up to 3,000 users, both manual and automated, based on real data.
This architect... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: 'Reference architecture: Up to 60 RPS or 3,000 users'
breadcrumbs:
- doc
- administrat... |
https://docs.gitlab.com/administration/25k_users | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/25k_users.md | 2025-08-13 | doc/administration/reference_architectures | [
"doc",
"administration",
"reference_architectures"
] | 25k_users.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Reference architecture: Up to 500 RPS or 25,000 users | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This page describes the GitLab reference architecture designed to target a peak load of 500 requests per second (RPS) - The typical peak load of up to 25,000 users, both manual and automated, based on real data.
For a full ... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: 'Reference architecture: Up to 500 RPS or 25,000 users'
breadcrumbs:
- doc
- administr... |
https://docs.gitlab.com/administration/1k_users | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/1k_users.md | 2025-08-13 | doc/administration/reference_architectures | [
"doc",
"administration",
"reference_architectures"
] | 1k_users.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Reference architecture: Up to 20 RPS or 1,000 users | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This reference architecture targets a peak load of 20 requests per second (RPS). Based on real data, this load typically corresponds to up to 1,000 users, which includes both manual and automated interactions.
For a f... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: 'Reference architecture: Up to 20 RPS or 1,000 users'
breadcrumbs:
- doc
- administrat... |
https://docs.gitlab.com/administration/50k_users | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/50k_users.md | 2025-08-13 | doc/administration/reference_architectures | [
"doc",
"administration",
"reference_architectures"
] | 50k_users.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Reference architecture: Up to 1000 RPS or 50,000 users | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This page describes the GitLab reference architecture designed to target a peak load of 1000 requests per second (RPS), the typical peak load of up to 50,000 users, both manual and automated, based on real data.
For a full ... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: 'Reference architecture: Up to 1000 RPS or 50,000 users'
breadcrumbs:
- doc
- administ... |
https://docs.gitlab.com/administration/2k_users | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/2k_users.md | 2025-08-13 | doc/administration/reference_architectures | [
"doc",
"administration",
"reference_architectures"
] | 2k_users.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Reference architecture: Up to 40 RPS or 2,000 users | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This page describes the GitLab reference architecture designed to target a peak load of 40 requests per second (RPS), the typical peak load of up to 2,000 users, both manual and automated, based on real data.
For a fu... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: 'Reference architecture: Up to 40 RPS or 2,000 users'
breadcrumbs:
- doc
- administrat... |
https://docs.gitlab.com/administration/reference_architectures | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/_index.md | 2025-08-13 | doc/administration/reference_architectures | [
"doc",
"administration",
"reference_architectures"
] | _index.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Reference architectures | Recommended deployments at scale. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
The GitLab reference architectures are validated, production-ready environment designs for deploying GitLab at scale. Each architecture provides detailed specifications that you can use or adapt based on your requireme... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Recommended deployments at scale.
title: Reference architectures
breadcrumbs:
- ... |
https://docs.gitlab.com/administration/10k_users | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/10k_users.md | 2025-08-13 | doc/administration/reference_architectures | [
"doc",
"administration",
"reference_architectures"
] | 10k_users.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Reference architecture: Up to 200 RPS or 10,000 users | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This page describes the GitLab reference architecture designed to target a peak load of 200 requests per second (RPS), the typical peak load of up to 10,000 users, both manual and automated, based on real data.
For a full l... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: 'Reference architecture: Up to 200 RPS or 10,000 users'
breadcrumbs:
- doc
- administr... |
https://docs.gitlab.com/administration/5k_users | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/5k_users.md | 2025-08-13 | doc/administration/reference_architectures | [
"doc",
"administration",
"reference_architectures"
] | 5k_users.md | GitLab Delivery | Self Managed | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Reference architecture: Up to 100 RPS or 5,000 users | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This page describes the GitLab reference architecture designed to target a peak load of 100 requests per second (RPS) - The typical peak load of up to 5,000 users, both manual and automated, based on real data.
For a full l... | ---
stage: GitLab Delivery
group: Self Managed
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: 'Reference architecture: Up to 100 RPS or 5,000 users'
breadcrumbs:
- doc
- administra... |
https://docs.gitlab.com/administration/configuration_types | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/configuration_types.md | 2025-08-13 | doc/administration/gitlab_duo_self_hosted | [
"doc",
"administration",
"gitlab_duo_self_hosted"
] | configuration_types.md | AI-powered | Custom Models | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | GitLab Duo Self-Hosted configuration and authentication | Get started with GitLab Duo Self-Hosted. |
{{< details >}}
- Tier: Premium, Ultimate
- Add-on: GitLab Duo Enterprise
- Offering: GitLab Self-Managed
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/12972) in GitLab 17.1 [with a flag](../feature_flags/_index.md) named `ai_custom_model`. Disabled by default.
- [En... | ---
stage: AI-powered
group: Custom Models
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Get started with GitLab Duo Self-Hosted.
title: GitLab Duo Self-Hosted configuration... |
https://docs.gitlab.com/administration/supported_llm_serving_platforms | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/supported_llm_serving_platforms.md | 2025-08-13 | doc/administration/gitlab_duo_self_hosted | [
"doc",
"administration",
"gitlab_duo_self_hosted"
] | supported_llm_serving_platforms.md | AI-powered | Custom Models | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | GitLab Duo Self-Hosted supported platforms | Supported LLM Serving Platforms. |
{{< details >}}
- Tier: Premium, Ultimate
- Add-on: GitLab Duo Enterprise
- Offering: GitLab Self-Managed
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/12972) in GitLab 17.1 [with a flag](../feature_flags/_index.md) named `ai_custom_model`. Disabled by default.
- [En... | ---
stage: AI-powered
group: Custom Models
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Supported LLM Serving Platforms.
title: GitLab Duo Self-Hosted supported platforms
b... |
https://docs.gitlab.com/administration/supported_models_and_hardware_requirements | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/supported_models_and_hardware_requirements.md | 2025-08-13 | doc/administration/gitlab_duo_self_hosted | [
"doc",
"administration",
"gitlab_duo_self_hosted"
] | supported_models_and_hardware_requirements.md | AI-powered | Custom Models | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Supported GitLab Duo Self-Hosted models and hardware requirements | Supported models and hardware requirements. |
{{< details >}}
- Tier: Premium, Ultimate
- Add-on: GitLab Duo Enterprise
- Offering: GitLab Self-Managed
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/12972) in GitLab 17.1 [with a flag](../feature_flags/_index.md) named `ai_custom_model`. Disabled by default.
- [En... | ---
stage: AI-powered
group: Custom Models
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Supported models and hardware requirements.
title: Supported GitLab Duo Self-Hosted ... |
https://docs.gitlab.com/administration/gitlab_duo_self_hosted | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/_index.md | 2025-08-13 | doc/administration/gitlab_duo_self_hosted | [
"doc",
"administration",
"gitlab_duo_self_hosted"
] | _index.md | AI-powered | Custom Models | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | GitLab Duo Self-Hosted | Host your own AI gateway and language models. |
{{< details >}}
- Tier: Premium, Ultimate
- Add-on: GitLab Duo Enterprise
- Offering: GitLab Self-Managed
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/12972) in GitLab 17.1 [with a flag](../feature_flags/_index.md) named `ai_custom_model`. Disabled by default.
- [En... | ---
stage: AI-powered
group: Custom Models
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Host your own AI gateway and language models.
title: GitLab Duo Self-Hosted
breadcru... |
https://docs.gitlab.com/administration/logging | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/logging.md | 2025-08-13 | doc/administration/gitlab_duo_self_hosted | [
"doc",
"administration",
"gitlab_duo_self_hosted"
] | logging.md | AI-powered | Custom Models | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Enable logging for self-hosted models | Enable logging for self-hosted models. |
{{< details >}}
- Tier: Premium, Ultimate
- Add-on: GitLab Duo Enterprise
- Offering: GitLab Self-Managed
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/12972) in GitLab 17.1 [with a flag](../feature_flags/_index.md) named `ai_custom_model`. Disabled by default.
- [En... | ---
stage: AI-powered
group: Custom Models
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Enable logging for self-hosted models.
title: Enable logging for self-hosted models
... |
https://docs.gitlab.com/administration/configure_duo_features | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/configure_duo_features.md | 2025-08-13 | doc/administration/gitlab_duo_self_hosted | [
"doc",
"administration",
"gitlab_duo_self_hosted"
] | configure_duo_features.md | AI-powered | Custom Models | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Configure GitLab to access GitLab Duo Self-Hosted | Configure your GitLab instance to use GitLab Duo Self-Hosted. |
{{< details >}}
- Tier: Premium, Ultimate
- Add-on: GitLab Duo Enterprise
- Offering: GitLab Self-Managed
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/12972) in GitLab 17.1 [with a flag](../feature_flags/_index.md) named `ai_custom_model`. Disabled by default.
- [En... | ---
stage: AI-powered
group: Custom Models
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Configure your GitLab instance to use GitLab Duo Self-Hosted.
title: Configure GitLa... |
https://docs.gitlab.com/administration/troubleshooting | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/troubleshooting.md | 2025-08-13 | doc/administration/gitlab_duo_self_hosted | [
"doc",
"administration",
"gitlab_duo_self_hosted"
] | troubleshooting.md | AI-powered | Custom Models | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting GitLab Duo Self-Hosted | Troubleshooting tips for deploying GitLab Duo Self-Hosted |
{{< details >}}
- Tier: Premium, Ultimate
- Add-on: GitLab Duo Enterprise
- Offering: GitLab Self-Managed
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/12972) in GitLab 17.1 [with a flag](../feature_flags/_index.md) named `ai_custom_model`. Disabled by default.
- [En... | ---
stage: AI-powered
group: Custom Models
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Troubleshooting tips for deploying GitLab Duo Self-Hosted
title: Troubleshooting Git... |
https://docs.gitlab.com/administration/support_engineer_playbook | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/support_engineer_playbook.md | 2025-08-13 | doc/administration/gitlab_duo_self_hosted | [
"doc",
"administration",
"gitlab_duo_self_hosted"
] | support_engineer_playbook.md | AI-powered | Custom Models | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | GitLab Duo Self-Hosted Support Engineer Playbook | Troubleshooting tips for GitLab Duo Self-Hosted |
{{< details >}}
- Tier: Premium, Ultimate
- Add-on: GitLab Duo Enterprise
- Offering: GitLab Self-Managed
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/12972) in GitLab 17.1 [with a flag](../feature_flags/_index.md) named `ai_custom_model`. Disabled by default.
- [En... | ---
stage: AI-powered
group: Custom Models
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Troubleshooting tips for GitLab Duo Self-Hosted
title: GitLab Duo Self-Hosted Suppor... |
https://docs.gitlab.com/administration/snippets | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/_index.md | 2025-08-13 | doc/administration/snippets | [
"doc",
"administration",
"snippets"
] | _index.md | Create | Source Code | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Snippets | Configure snippets settings for your GitLab instance. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
To prevent abuse of snippets on your instance, configure a maximum snippet size that is enforced
when users create or update snippets. Existing snippets are not affected by the limit unless a
user updates them, and the... | ---
stage: Create
group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Configure snippets settings for your GitLab instance.
title: Snippets
breadcrumbs:
- doc
-... |
https://docs.gitlab.com/administration/maintenance_mode | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/_index.md | 2025-08-13 | doc/administration/maintenance_mode | [
"doc",
"administration",
"maintenance_mode"
] | _index.md | Tenant Scale | Geo | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | GitLab Maintenance Mode | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
Maintenance Mode allows administrators to reduce write operations to a minimum while maintenance tasks are performed. The main goal is to block all external actions that change the internal state. The internal state includes... | ---
stage: Tenant Scale
group: Geo
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: GitLab Maintenance Mode
breadcrumbs:
- doc
- administration
- maintenance_mode
---
{{< details >... |
https://docs.gitlab.com/administration/crowd | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/crowd.md | 2025-08-13 | doc/administration/auth | [
"doc",
"administration",
"auth"
] | crowd.md | Software Supply Chain Security | Authentication | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Use Atlassian Crowd as an authentication provider | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
Authenticate to GitLab using the Atlassian Crowd OmniAuth provider. Enabling
this provider also allows Crowd authentication for Git-over-https requests.
## Configure a new Crowd application
1. On the top menu, select... | ---
stage: Software Supply Chain Security
group: Authentication
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Use Atlassian Crowd as an authentication provider
breadcrumbs:
- doc
... |
https://docs.gitlab.com/administration/smartcard | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/smartcard.md | 2025-08-13 | doc/administration/auth | [
"doc",
"administration",
"auth"
] | smartcard.md | Software Supply Chain Security | Authentication | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Smart card authentication | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
GitLab supports authentication using smart cards.
## Existing password authentication
By default, existing users can continue to sign in with a username and password when smart card
authentication is enabled.
To force exi... | ---
stage: Software Supply Chain Security
group: Authentication
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Smart card authentication
breadcrumbs:
- doc
- administration
- auth
... |
https://docs.gitlab.com/administration/jwt | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/jwt.md | 2025-08-13 | doc/administration/auth | [
"doc",
"administration",
"auth"
] | jwt.md | Software Supply Chain Security | Authentication | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Use JWT as an authentication provider | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
To enable the JWT OmniAuth provider, you must register your application with JWT.
JWT provides you with a secret key for you to use.
1. On your GitLab server, open the configuration file.
For Linux package install... | ---
stage: Software Supply Chain Security
group: Authentication
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Use JWT as an authentication provider
breadcrumbs:
- doc
- administra... |
https://docs.gitlab.com/administration/atlassian | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/atlassian.md | 2025-08-13 | doc/administration/auth | [
"doc",
"administration",
"auth"
] | atlassian.md | Software Supply Chain Security | Authentication | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Use Atlassian as an OAuth 2.0 authentication provider | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
To enable the Atlassian OmniAuth provider for passwordless authentication you must register an application with Atlassian.
## Atlassian application registration
1. Go to the [Atlassian developer console](https://deve... | ---
stage: Software Supply Chain Security
group: Authentication
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Use Atlassian as an OAuth 2.0 authentication provider
breadcrumbs:
- ... |
https://docs.gitlab.com/administration/oidc | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/oidc.md | 2025-08-13 | doc/administration/auth | [
"doc",
"administration",
"auth"
] | oidc.md | Software Supply Chain Security | Authentication | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Use OpenID Connect as an authentication provider | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
You can use GitLab as a client application with [OpenID Connect](https://openid.net/specs/openid-connect-core-1_0.html)
as an OmniAuth provider.
To enable the OpenID Connect OmniAuth provider, you must register your a... | ---
stage: Software Supply Chain Security
group: Authentication
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Use OpenID Connect as an authentication provider
breadcrumbs:
- doc
-... |
https://docs.gitlab.com/administration/cognito | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/cognito.md | 2025-08-13 | doc/administration/auth | [
"doc",
"administration",
"auth"
] | cognito.md | Software Supply Chain Security | Authentication | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Use AWS Cognito as an OAuth 2.0 authentication provider | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
Amazon Web Services (AWS) Cognito lets you add user sign-up, sign-in, and access control to your GitLab instance.
The following documentation enables AWS Cognito as an OAuth 2.0 provider.
## Configure AWS Cognito
To ... | ---
stage: Software Supply Chain Security
group: Authentication
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Use AWS Cognito as an OAuth 2.0 authentication provider
breadcrumbs:
... |
https://docs.gitlab.com/administration/test_oidc_oauth | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/test_oidc_oauth.md | 2025-08-13 | doc/administration/auth | [
"doc",
"administration",
"auth"
] | test_oidc_oauth.md | Software Supply Chain Security | Authentication | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Test OIDC/OAuth in GitLab | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
To test OIDC/OAuth in GitLab, you must:
1. [Enable OIDC/OAuth](#enable-oidcoauth-in-gitlab)
1. [Test OIDC/OAuth with your client application](#test-oidcoauth-with-your-client-application)
1. [Verify OIDC/OAuth authent... | ---
stage: Software Supply Chain Security
group: Authentication
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Test OIDC/OAuth in GitLab
breadcrumbs:
- doc
- administration
- auth
... |
https://docs.gitlab.com/administration/auth | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/_index.md | 2025-08-13 | doc/administration/auth | [
"doc",
"administration",
"auth"
] | _index.md | Software Supply Chain Security | Authentication | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | GitLab authentication and authorization | Third-party authentication providers. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
GitLab integrates with a number of [OmniAuth providers](../../integration/omniauth.md#supported-providers),
and the following external authentication and authorization providers:
- [LDAP](ldap/_index.md): Includes Act... | ---
stage: Software Supply Chain Security
group: Authentication
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Third-party authentication providers.
title: GitLab authenticat... |
https://docs.gitlab.com/administration/auth/ldap_synchronization | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/auth/ldap_synchronization.md | 2025-08-13 | doc/administration/auth/ldap | [
"doc",
"administration",
"auth",
"ldap"
] | ldap_synchronization.md | Fulfillment | Seat Management | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | LDAP synchronization | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
If you have [configured LDAP to work with GitLab](_index.md), GitLab can automatically synchronize
users and groups.
LDAP synchronization updates user and group information for existing GitLab users that have an LDAP identi... | ---
stage: Fulfillment
group: Seat Management
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
gitlab_dedicated: false
title: LDAP synchronization
breadcrumbs:
- doc
- administration
- auth... |
https://docs.gitlab.com/administration/auth/ldap-troubleshooting | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/auth/ldap-troubleshooting.md | 2025-08-13 | doc/administration/auth/ldap | [
"doc",
"administration",
"auth",
"ldap"
] | ldap-troubleshooting.md | Software Supply Chain Security | Authentication | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting LDAP | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
If you are an administrator, use the following information to troubleshoot LDAP.
## Common Problems & Workflows
### Connection
#### Connection refused
If you're getting `Connection Refused` error messages when atte... | ---
stage: Software Supply Chain Security
group: Authentication
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting LDAP
breadcrumbs:
- doc
- administration
- auth
- lda... |
https://docs.gitlab.com/administration/auth/google_secure_ldap | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/auth/google_secure_ldap.md | 2025-08-13 | doc/administration/auth/ldap | [
"doc",
"administration",
"auth",
"ldap"
] | google_secure_ldap.md | Software Supply Chain Security | Authentication | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Google Secure LDAP | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
[Google Cloud Identity](https://cloud.google.com/identity/) provides a Secure
LDAP service that can be configured with GitLab for authentication and group sync.
Secure LDAP requires a slightly different configuration ... | ---
stage: Software Supply Chain Security
group: Authentication
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Google Secure LDAP
breadcrumbs:
- doc
- administration
- auth
- ldap
... |
https://docs.gitlab.com/administration/auth/ldap | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/auth/_index.md | 2025-08-13 | doc/administration/auth/ldap | [
"doc",
"administration",
"auth",
"ldap"
] | _index.md | Software Supply Chain Security | Authentication | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Integrate LDAP with GitLab | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
GitLab integrates with [LDAP - Lightweight Directory Access Protocol](https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol)
to support user authentication.
This integration works with most LDAP-complian... | ---
stage: Software Supply Chain Security
group: Authentication
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
gitlab_dedicated: false
title: Integrate LDAP with GitLab
breadcrumbs:
- doc... |
https://docs.gitlab.com/administration/lfs | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/_index.md | 2025-08-13 | doc/administration/lfs | [
"doc",
"administration",
"lfs"
] | _index.md | Create | Source Code | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | GitLab Git Large File Storage (LFS) Administration | Configure Git LFS for GitLab Self-Managed. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
Use Git Large File Storage (LFS) to store large files in a Git repository without
increasing its size or affecting performance. You can enable or disable LFS, configure local
or remote storage for LFS objects, and migr... | ---
stage: Create
group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Configure Git LFS for GitLab Self-Managed.
title: GitLab Git Large File Storage (LFS) Admi... |
https://docs.gitlab.com/administration/replication_and_failover | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/replication_and_failover.md | 2025-08-13 | doc/administration/redis | [
"doc",
"administration",
"redis"
] | replication_and_failover.md | Data access | Durability | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Redis replication and failover with the Linux package | null |
{{< details >}}
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
This documentation is for the Linux package. To use your own
non-bundled Redis, see [Redis replication and failover providing your own instance](replication_and_failover_external.md).
In Redis lingo, `primary` is called `ma... | ---
stage: Data access
group: Durability
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Redis replication and failover with the Linux package
breadcrumbs:
- doc
- administration
- ... |
https://docs.gitlab.com/administration/redis | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/_index.md | 2025-08-13 | doc/administration/redis | [
"doc",
"administration",
"redis"
] | _index.md | Data access | Durability | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Configuring Redis for scaling | Configure Redis for scaling. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
Based on your infrastructure setup and how you have installed GitLab, there are
multiple ways to configure Redis.
You can choose to install and manage Redis and Sentinel yourself, use a hosted
cloud solution, or you c... | ---
stage: Data access
group: Durability
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Configuring Redis for scaling
description: Configure Redis for scaling.
breadcrumbs:
- doc
-... |
https://docs.gitlab.com/administration/troubleshooting | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/troubleshooting.md | 2025-08-13 | doc/administration/redis | [
"doc",
"administration",
"redis"
] | troubleshooting.md | Data access | Durability | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting Redis | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
There are a lot of moving parts that must be taken care carefully
in order for the HA setup to work as expected.
Before proceeding with the troubleshooting below, check your firewall rules:
- Redis machines
- Accep... | ---
stage: Data access
group: Durability
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting Redis
breadcrumbs:
- doc
- administration
- redis
---
{{< details >}}
- T... |
https://docs.gitlab.com/administration/replication_and_failover_external | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/replication_and_failover_external.md | 2025-08-13 | doc/administration/redis | [
"doc",
"administration",
"redis"
] | replication_and_failover_external.md | Data access | Durability | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Redis replication and failover providing your own instance | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
If you're hosting GitLab on a cloud provider, you can optionally use a managed
service for Redis. For example, AWS offers ElastiCache that runs Redis.
Alternatively, you may opt to manage your own Redis instance separ... | ---
stage: Data access
group: Durability
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Redis replication and failover providing your own instance
breadcrumbs:
- doc
- administrati... |
https://docs.gitlab.com/administration/standalone | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/administration/standalone.md | 2025-08-13 | doc/administration/redis | [
"doc",
"administration",
"redis"
] | standalone.md | Data access | Durability | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Standalone Redis using the Linux package | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
The Linux package can be used to configure a standalone Redis server.
In this configuration, Redis is not scaled, and represents a single
point of failure. However, in a scaled environment the objective is to allow
the... | ---
stage: Data access
group: Durability
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Standalone Redis using the Linux package
breadcrumbs:
- doc
- administration
- redis
---
{... |
https://docs.gitlab.com/error_tracking | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/error_tracking.md | 2025-08-13 | doc/operations | [
"doc",
"operations"
] | error_tracking.md | Monitor | Platform Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Error Tracking | Error tracking, logging, debugging, and data retention. |
Error Tracking helps developers to discover and view errors generated by their
application. Because error information is surfaced where the code is developed,
error tracking increases efficiency and awareness. Users can choose between
[GitLab Integrated error tracking](integrated_error_tracking.md) and
[Sentry-based]... | ---
stage: Monitor
group: Platform Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Error Tracking
description: Error tracking, logging, debugging, and data retention.
bread... |
https://docs.gitlab.com/operations | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/_index.md | 2025-08-13 | doc/operations | [
"doc",
"operations"
] | _index.md | Monitor | Platform Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Monitor your application | Track errors and manage incident response. |
Visualize and analyze errors and incidents related to your application and its infrastructure.
{{< cards >}}
- [Getting started](../user/get_started/get_started_monitoring.md)
- [Error tracking](error_tracking.md)
- [Incident management](incident_management/_index.md)
- [Observability](observability.md)
{{< /cards... | ---
stage: Monitor
group: Platform Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Track errors and manage incident response.
title: Monitor your application
breadcru... |
https://docs.gitlab.com/integrated_error_tracking | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/integrated_error_tracking.md | 2025-08-13 | doc/operations | [
"doc",
"operations"
] | integrated_error_tracking.md | Monitor | Platform Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Integrated error tracking | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com
{{< /details >}}
This guide provides basic information on how to set up integrated error tracking for
your project, using examples from different languages.
Error tracking provided by GitLab Observability is based on
[Sentry SDK](https://docs.... | ---
stage: Monitor
group: Platform Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Integrated error tracking
breadcrumbs:
- doc
- operations
---
{{< details >}}
- Tier: ... |
https://docs.gitlab.com/feature_flags | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/feature_flags.md | 2025-08-13 | doc/operations | [
"doc",
"operations"
] | feature_flags.md | Deploy | Environments | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Feature flags | Progressive delivery, controlled deployment, and risk reduction. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
With feature flags, you can deploy your application's new features to production in smaller batches.
You can toggle a feature on and off to subsets of users, helping you achieve Continuous... | ---
stage: Deploy
group: Environments
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Progressive delivery, controlled deployment, and risk reduction.
title: Feature flags
bre... |
https://docs.gitlab.com/sentry_error_tracking | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/sentry_error_tracking.md | 2025-08-13 | doc/operations | [
"doc",
"operations"
] | sentry_error_tracking.md | Monitor | Platform Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Sentry error tracking | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
[Sentry](https://sentry.io/) is an open source error tracking system. GitLab enables
administrators to connect Sentry to GitLab, so users can view a list of Sentry errors in GitLab.
GitLa... | ---
stage: Monitor
group: Platform Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Sentry error tracking
breadcrumbs:
- doc
- operations
---
{{< details >}}
- Tier: Free... |
https://docs.gitlab.com/observability | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/observability.md | 2025-08-13 | doc/operations | [
"doc",
"operations"
] | observability.md | none | Embody | This page is owned by https://handbook.gitlab.com/handbook/ceo/office-of-the-ceo/embody-team/ | Observability | Monitor application performance and troubleshoot performance issues. |
{{< details >}}
- Tier: Free
- Offering: GitLab Self-Managed
- Status: Experimental
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/experimental-observability/documentation/-/issues/6) in GitLab 18.1. This feature is an [experiment](../policy/development_stages_support.md).
{{< /history >}}
{... | ---
stage: none
group: Embody
info: This page is owned by https://handbook.gitlab.com/handbook/ceo/office-of-the-ceo/embody-team/
description: Monitor application performance and troubleshoot performance issues.
ignore_in_report: true
title: Observability
breadcrumbs:
- doc
- operations
---
{{< details >}}
- Tier: F... |
https://docs.gitlab.com/operations/incident_timeline_events | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/operations/incident_timeline_events.md | 2025-08-13 | doc/operations/incident_management | [
"doc",
"operations",
"incident_management"
] | incident_timeline_events.md | Monitor | Platform Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Timeline events | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/344059) in GitLab 15.2 [with a flag](../../administration/feature_flags/_index.md) named `incident_timeline`. ... | ---
stage: Monitor
group: Platform Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Timeline events
breadcrumbs:
- doc
- operations
- incident_management
---
{{< details >... |
https://docs.gitlab.com/operations/incident_management | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/operations/_index.md | 2025-08-13 | doc/operations/incident_management | [
"doc",
"operations",
"incident_management"
] | _index.md | Monitor | Platform Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Incident management | Alert handling, response coordination, and escalation procedures. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< alert type="note" >}}
This feature is not under active development, but [community contributions](https://about.gitlab.com/community/contribute/) are welcome.
For more information, se... | ---
stage: Monitor
group: Platform Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Incident management
description: Alert handling, response coordination, and escalation pr... |
https://docs.gitlab.com/operations/manage_incidents | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/operations/manage_incidents.md | 2025-08-13 | doc/operations/incident_management | [
"doc",
"operations",
"incident_management"
] | manage_incidents.md | Monitor | Platform Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Manage incidents | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- Ability to add an [incident](_index.md) to an iteration [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/347153) in GitLab 17.0.
{{< /history >}}
This page c... | ---
stage: Monitor
group: Platform Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Manage incidents
breadcrumbs:
- doc
- operations
- incident_management
---
{{< details ... |
https://docs.gitlab.com/operations/incidents | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/operations/incidents.md | 2025-08-13 | doc/operations/incident_management | [
"doc",
"operations",
"incident_management"
] | incidents.md | Monitor | Platform Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Incidents | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
An incident is a service disruption or outage that needs to be restored urgently.
Incidents are critical in incident management workflows.
Use GitLab to triage, respond, and remediate inci... | ---
stage: Monitor
group: Platform Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Incidents
breadcrumbs:
- doc
- operations
- incident_management
---
{{< details >}}
- ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.