The symptom you get if you leave it as https is continual and unstoppable 422 errors, well documented on gitlab's forums. This is a sufficient workaround until this known issue is fixed. Even though it lists project repositories as 'http' within the gitlab instance, it redirects to https as per the vhost in apache. This is because I already built Let's Encrypt certificates and set up TLS on the website before I installed gitlab. These are the options I used with my LAMP stack to get it up and running:īefore I discuss the other configuration options, let me point out that I have to keep this as http and not https, letting my apache vhost redirect to https instead of building it into the gitlab server configuration, in order to work. The requests an additional line - which I included but commented out - be adjusted and also forgets to specify that gitlab_workhorse should be enabled. Now that that is done, let's begin by installing Gitlab Community Edition and editing the Ruby configuration file to work with the LAMP stack: This script will allow you to access the repositories and download gitlab-ce. The first thing you need to do is download and run the script that gitlab provides. If you are missing some of these pre-requisites, please visit the I created which covers these topics. * Letsencrypt, using certbot, is established and working * Self-Signed Certificate is established as backup * Self Hosted Web Server using Apache 2.4

How to install gitlab ce