I just installed a fresh install of GitLab-CE on Ubuntu 16.04 using apt. I already had apache running on the server so had to set up a virtual host and stuff for GitLab. Everything is displaying but with no CSS and if I try to login, request password, etc… I get a 422 error.

According to “gitlab-ctl status” all the services are running. Here is my gitlab.conf (virtual host file in apache).

<VirtualHost *:80>
ServerName gitlab.mystuff.com
ServerSignature Off

ProxyPreserveHost On

ProxyPassReverse http://127.0.0.1:8080
ProxyPassReverse http://gitlab.mystuff.com

RewriteEngine on
RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
RewriteRule .* http://127.0.0.1:8080%{REQUEST_URI} [P,QSA]

needed for downloading attachments

DocumentRoot /opt/gitlab/embedded/service/gitlab-rails/public

I found that the https designation in /etc/gitlab/gitlab.rb was causing this. Just manually set up your vhost and letsencrypt first, using the appropriate Apache recipe, etc., and then specify http in the gitlab.rb, letting apache do the redirection to https instead of the gitlab server and then it works - no more 422. It lists repositories as having http access, but they also redirect as per the vhost settings when one clone’s the repository. I have a tutorial for what I did here.

For those who find this, I found his tutorial at this updated link: