Package defaults

  • Tier: Free, Premium, Ultimate
  • Offering: GitLab Self-Managed

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:

ComponentOn by defaultCommunicates viaAlternativeConnection port
GitLab RailsYesPort80 or 443
GitLab ShellYesPort22
PostgreSQLYesSocketPort (5432)
RedisYesSocketPort (6379)
PumaYesSocketPort (8080)
GitLab WorkhorseYesSocketPort (8181)
NGINX statusYesPort8060
PrometheusYesPort9090
Node exporterYesPort9100
Redis exporterYesPort9121
PostgreSQL exporterYesPort9187
PgBouncer exporterNoPort9188
GitLab ExporterYesPort9168
Sidekiq exporterYesPort8082
Sidekiq health checkYesPort8092 1
Web exporterNoPort8083
Geo PostgreSQLNoSocketPort (5431)
Redis SentinelNoPort26379
Incoming emailNoPort143
Elastic searchNoPort9200
GitLab PagesNoPort80 or 443
GitLab RegistryNo*Port80, 443 or 5050
GitLab RegistryNoPort5000
LDAPNoPortDepends on the component configuration
KerberosNoPort8443 or 8088
OmniAuthYesPortDepends on the component configuration
SMTPNoPort465
Remote syslogNoPort514
MattermostNoPort8065
MattermostNoPort80 or 443
PgBouncerNoPort6432
ConsulNoPort8300, 8301(TCP and UDP), 8500, 8600 2
PatroniNoPort8008
GitLab KASYesPort8150
GitalyYesSocketPort (8075)8075 or 9999 (TLS)
Gitaly exporterYesPort9236
PraefectNoPort2305 or 3305 (TLS)
GitLab Workhorse exporterYesPort9229
Registry exporterNoPort5001

Footnotes:

  1. If Sidekiq health check settings are not set, they default to the Sidekiq metrics exporter settings. This default is deprecated and is set to be removed in GitLab 15.0.
  2. If using additional Consul functionality, more ports may need to be opened. See the official documentation for the list.

Legend:

  • Component - Name of the component.
  • On by default - Is the component running by default.
  • Communicates via - How the component talks with the other components.
  • Alternative - If it is possible to configure the component to use different type of communication. The type is listed with default port used in that case.
  • Connection port - Port on which the component communicates.

GitLab also expects a file system to be ready for the storage of Git repositories and various other files.

If you are using NFS (Network File System), files are carried over a network which requires, based on implementation, ports 111 and 2049 to be open.

In some cases, the GitLab Registry is automatically enabled by default. For more information, see GitLab container registry administration.