Also replace YOUR_CERTIFICATE_FILE and YOUR_CA_CERTIFICATE_FILE with the file names we just found out. Replace YOUR_SERVER_FQDN with your domain name (6 times). The file names are obfuscated by Plesk, but you can find out which is the right one by having a look at the last Apache or nginx config files of your domain as described here.

* Next up for HTTPS we will need the file names of the Let’s Encrypt files we created earlier. # You can live without it but clients will have to type in to reach gitlab. # This section is only needed if you want to redirect http traffic to https. # listen on port 8181, edit /etc/gitlab/gitlab.rb and change the following: # gitlab-workhorse is listening on port 8181. # Note this config assumes unicorn is listening on default port 8080 and

Replace YOUR_SERVER_FQDN with your domain name (without # This configuration has been tested on GitLab 8.2 We will use the contents of the file nf and adjust them to our needs. Go to Apache & nginx Settings of the domain. Apply the web server configs in Plesk.Apply the changes to /etc/gitlab/gitlab.rb.We can skip the trusted proxies, but we need to do the optional step because we are using Apache as web-server.Replace plesk_user with the username for the webspace of the domain. Edit the /etc/gitlab/gitlab.rb config file.Disable the bundled web-server as described here.sudo EXTERNAL_URL='' apt-get install gitlab-ee Replace with your FQDN and make sure the URL starts with https. Sudo apt-get install -y curl openssh-server ca-certificates postfix

Install Omnibus GitLab as described here.

Secure the domain with Let’s Encrypt as described here.

In Plesk create a new domain or subdomain, e.g.

For anyone having the same idea, here is how I did it step by step. After fiddling around for two days with installing packages, adjusting configs and restarting services, I finally got GitLab to work on my Virtual Server with Plesk Onyx and SSL encryption.

How to install gitlab on ubuntu server