GitLAB self-managed Installation

Hi , I am installing GIT LAB self-manged with EE (core) on CentOS7.Following Documnet : . The requirement says to install Ruby,Go,GIT,node.js and Postgres DB . The installation steps is to follow . Following are my queries ,
1 . Am i referring correct documents ?
2. What is the use of Postgres DB installation

Do refer the GitLab docs. I think GitLab docs has answers to all your queries.

Hi @vmr1234! Good suggestion, our docs are great. It would be even more helpful to link to a specific doc you think would help the original poster the most. Thanks!

1 Like

@Vasavi @Linds
Correct.You should see the documents to install it.

1. Install and configure the necessary dependencies

On CentOS 7 (and RedHat/Oracle/Scientific Linux 7), the commands below will also open HTTP, HTTPS and SSH access in the system firewall.

sudo yum install -y curl policycoreutils-python openssh-server 
sudo systemctl enable sshd 
sudo systemctl start sshd sudo firewall-cmd --permanent --add-service=http 
sudo firewall-cmd --permanent --add-service=https 
sudo systemctl reload firewalld

Next, install Postfix to send notification emails. If you want to use another solution to send emails please skip this step and configure an external SMTP server after GitLab has been installed.

sudo yum install postfix sudo systemctl enable postfix sudo systemctl start postfix

During Postfix installation a configuration screen may appear. Select ‘Internet Site’ and press enter. Use your server’s external DNS for ‘mail name’ and press enter. If additional screens appear, continue to press enter to accept the defaults.

2. Add the GitLab package repository and install the package

Add the GitLab package repository.

curl | sudo bash

Next, install the GitLab package. Change to the URL at which you want to access your GitLab instance. Installation will automatically configure and start GitLab at that URL.

For https:// URLs GitLab will automatically request a certificate with Let’s Encrypt, which requires inbound HTTP access and a valid hostname. You can also use your own certificate or just use http://.

sudo EXTERNAL_URL="" yum install -y gitlab-ee

3. Browse to the hostname and login

On your first visit, you’ll be redirected to a password reset screen. Provide the password for the initial administrator account and you will be redirected back to the login screen. Use the default account’s username root to login.

See our documentation for detailed instructions on installing and configuration.

4. Set up your communication preferences

Visit our email subscription preference center to let us know when to communicate with you. We have an explicit email opt-in policy so you have complete control over what and how often we send you emails.

Twice a month, we send out the GitLab news you need to know, including new features, integrations, docs, and behind the scenes stories from our dev teams. For critical security updates related to bugs and system performance, sign up for our dedicated security newsletter.


What an amazing contribution to this thread :heart_eyes: !!! Thanks @sysdl132!

@Vasavi, let us know what you think!

Hi ,

I have installed required postgressql version .I need to know how to connect to this preferred DB .The Admin doc redirects to omnibus steps (the same which you have posted) , but i need to know how do i connect DB.

As of now i have followed omnibus steps and it has done all required, but i need to know how to connect to postgressql if we install the pre-requisites of preferred software versions .

Thank you in advance



the GitLab Omnibus package already provides a bundled PostgreSQL server, and also takes care about upgrades. You do not need to install or maintain your own PostgreSQL server for running GitLab. Can you elaborate on why you are going this route?


PS: @sysdl132 Amazing reply, thank you! That’s truly inspiring community work :heart:

Hi ,

Yes , i need to maintain my own postgresSQL DB.



follow along the documentation then please. Keep in mind that questions may remain unanswered on problems, the preferred and default way is to use the Omnibus provided setup.


1 Like

Hi ,

I have configure LDAP for GITLAB 12.10.3 . Am getting "Could not authenticate you from Ldapmain because "Connection reset by peer @ io fillbuf - fd:38 “.” error . I did run “sudo gitlab-ctl reconfigure” after configuring LDAP details .

Should i reboot GITLAB ?

Also , i see
1 . As per Link - “
gitlab_rails['verify_certificates'] = false :: I have set verify cert as false , as am using GITLAB EE core version

2 . am getting below error when i run “sudo gitlab-rake gitlab:check --trace” command
Exception: Connection reset by peer @ io_fillbuf - fd:18

Could any one help .

Thanks in advance

Hi All,

Any suggestion .


Hi Team ,

Any suggestion , kindly help .


You can try it with cloudron .It’s better than LDAP.
Try it in:

Its insisted to use LDAP only . Please could you help with LDAP error

Hi, says that verify_certificates being disabled will not solve the problem.

In order to analyse further, please provide the LDAP configuration from gitlab.rb (replace sensitive details) and the production.log entries whenever a login attempt is made by a client.

Also, check for possible whitespaces or other errors shown in this topic: [SOLVED] LDAP issue with Active Directory


1 Like