Skip to content

Latest commit

 

History

History
54 lines (47 loc) · 5.18 KB

defaults.md

File metadata and controls

54 lines (47 loc) · 5.18 KB

Package defaults

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

Ports

See the table below for the list of ports that the omnibus-gitlab 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
Unicorn 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
Postgres exporter Yes Port X 9187
Gitlab monitor Yes Port X 9168
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 or 443
GitLab Registry No Port X 5000
LDAP No Port X Depends on the component configuration
Kerberos No Port X 8443 or 8088
Omniauth No 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, 8500
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 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.