Package defaults

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


See the table below for the list of ports that the Omnibus GitLab assigns by default:

ComponentOn by defaultCommunicates viaAlternativeConnection port
GitLab RailsYesPortX80 or 443
GitLab ShellYesPortX22
PostgreSQLYesSocketPort (5432)X
RedisYesSocketPort (6379)X
UnicornYesSocketPort (8080)X
GitLab WorkhorseYesSocketPort (8181)X
NGINX statusYesPortX8060
Node exporterYesPortX9100
Redis exporterYesPortX9121
PostgreSQL exporterYesPortX9187
PgBouncer exporterNoPortX9188
GitLab ExporterYesPortX9168
Sidekiq exporterYesPortX8082
Unicorn exporterNoPortX8083
Puma exporterNoPortX8083
Geo PostgreSQLNoSocketPort (5431)X
Redis SentinelNoPortX26379
Incoming emailNoPortX143
Elastic searchNoPortX9200
GitLab PagesNoPortX80 or 443
GitLab RegistryNo*PortX80, 443 or 5050
GitLab RegistryNoPortX5000
LDAPNoPortXDepends on the component configuration
KerberosNoPortX8443 or 8088
OmniAuthYesPortXDepends on the component configuration
Remote syslogNoPortX514
MattermostNoPortX80 or 443
ConsulNoPortX8300, 8500


  • 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 filesystem to be ready for the storage of Git repositories and various other files.

Note that if you are using NFS (Network File System), files will be carried over a network which will require, based on implementation, ports 111 and 2049 to be open.

Note: In some cases, the GitLab Registry will be automatically enabled by default. Please see our documentation for more details