GitLab on a separate server behind an apache server

How to Use GitLab
1

Hi,

I had the following setup: A single server with a Plesk managed apache server on ports 80/443 and GitLab CE (omnibus) running on port 8081 (HTTPS). The vhost config of the apache was:

ServerName gitlab.some_url.de
Redirect permanent / https://gitlab.some_url.de

for HTTP and

ServerName gitlab.some_url.de
SSLEngine on
SSLProxyEngine on
ProxyRequests off
ProxyVia Off
ProxyPreserveHost on
<Proxy *>
   Order deny,allow
   Allow from all
</Proxy>
ProxyPass / https://localhost:8081/
ProxyPassReverse / https://localhost:8081/
<Location />
   Order allow,deny
   Allow from all
</Location>

for HTTPS and that worked fine.

Now I switched to a two server setup: Server 1 with Plesk and Server 2 with Gitlab (running on default ports this time). Both are in the same private subnet behind a router. Both servers running fine for their own. But the Proxy setting didn’t work anymore (of course I changed “https://localhost:8081/” in the settings above to the internal IP “https://192.168.10.2/”). All I get is an “empty response”.

Adding

ErrorLog  /var/log/apache2/gitlab_error.log
CustomLog /var/log/apache2/gitlab_access.log combined

to the config didn’t helped, because no entries are generated.

Of course I’ve used google :wink: but all “solutions” I’ve found did not change anything. And other solutions use load balancing stuff which I don’t need.

Can somebody please give me a hint?

1 Like
2

Hey did you find a solution to this yet??

I have sort of the same problem with one Apache2 web server with mod_proxy in front of the Gitlab instance