Gitlab Pages behind reverse Proxy Acces Control not working

Hello all,

we are using Gitlab Omnibus behind a nginx reverse proxy which works fine. I configured two IP-Addresses one for Pages and one for the Gitlab Pages

So gitlab-pages is listening to 192.168.0.100:80 and gitlab itself to 192.168.0.99:80 The Proxy fowards them via https as *.pages.domain.tld and gitlab.domain.tld

The configuration so far works fine. Now if some of our users want to use access control for pages and set the access to "Only Project Members"

image

They get the HTTP Response Code 403 Forbidden. I think the problem is because the Reverse Proxy is given as the remote address not the user itself but it wouldn't make any sense because the same would happen if it would not bee behind a Reverse Proxy.

image

The redirection is also successful but the url changes to something like that:

https://projects.pages.domain.tld/auth?domain=http://user.pages.domain.tld&state=8NQRRjcPDFZAcMG0ZC-ZKw==

Does someone got any ideas?

Best regards,

baltigx

Edited by Jason Plum