Multi-homed Gitlab site

Hi there,
I have a setup where Gitlab needs to be accessible from the Internet as well as from the local network.
Those two IPs and DNS names are different. For both I have the certificates (from godaddy) necessary.

The local network access can be accessed by users directly - https://gitlab.local.net/
From the Internet, the call goes to https://gitlab.external.net/
which goes to a web application firewall (which terminates the SSL traffic) and further goes to
https://gitlab.local.net/
The external_url setting in gitlab.rb is set to ‘https://gitlab.local.net’ which causes the correct
SSL certificates to load and all is good.
All this used to work without a hitch. After upgrading to 12.10.3-ee, the login and browsing in the repositories still works, but for whatever reason, the assets now use a full path which now looks like this:
https://gitlab.local.net/group/project/-/blob/master/resources.xml
Since the Internet does not know anything about gitlab.local.net, the call goes nowhere.
So the files cannot be edited online or looked at.
Any idea on how to solve this would be greatly appreciated.
Many thanks, Peter

Ok - I figured out a way to do it.
I am using now

external_url ‘https://gitlab.external.net/
nginx[‘ssl_certificate’] = “/etc/gitlab/ssl/gitlab.local.net.crt”
nginx[‘ssl_certificate_key’] = “/etc/gitlab/ssl/gitlab.local.net/key”

This setup works for me now externally and internally.

  • Cheers, Peter
1 Like