Package defaults

Tier: Free, Premium, Ultimate Offering: Self-managed

Unless configuration is specified in the /etc/gitlab/gitlab.rb file, the package assumes the defaults as noted below.


See the table below for the list of ports that the Linux package assigns by default:

Component On by default Communicates via Alternative Connection port
GitLab Rails Yes Port X 80 or 443
GitLab Shell Yes Port X 22
PostgreSQL Yes Socket Port (5432) X
Redis Yes Socket Port (6379) X
Puma Yes Socket Port (8080) X
GitLab Workhorse Yes Socket Port (8181) X
NGINX status Yes Port X 8060
Prometheus Yes Port X 9090
Node exporter Yes Port X 9100
Redis exporter Yes Port X 9121
PostgreSQL exporter Yes Port X 9187
PgBouncer exporter No Port X 9188
GitLab Exporter Yes Port X 9168
Sidekiq exporter Yes Port X 8082
Sidekiq health check Yes Port X 80921
Web exporter No Port X 8083
Geo PostgreSQL No Socket Port (5431) X
Redis Sentinel No Port X 26379
Incoming email No Port X 143
Elastic search No Port X 9200
GitLab Pages No Port X 80 or 443
GitLab Registry No* Port X 80, 443 or 5050
GitLab Registry No Port X 5000
LDAP No Port X Depends on the component configuration
Kerberos No Port X 8443 or 8088
OmniAuth Yes Port X Depends on the component configuration
SMTP No Port X 465
Remote syslog No Port X 514
Mattermost No Port X 8065
Mattermost No Port X 80 or 443
PgBouncer No Port X 6432
Consul No Port X 8300, 8301(TCP and UDP), 8500, 86002
Patroni No Port X 8008
GitLab KAS Yes Port X 8150
Gitaly Yes Socket Port (8075) 8075 or 9999 (TLS)
Gitaly exporter Yes Port X 9236
Praefect No Port X 2305 or 3305 (TLS)
GitLab Workhorse exporter Yes Port X 9229
Registry exporter No Port X 5001


  • 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. See our documentation for more details.
  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.