[DRE-maint] Bug#848872: gitlab: please document how to operate Debian gitlab behind an ssl terminating reverse proxy

Johannes Schauer josch at debian.org
Tue Dec 20 12:22:30 UTC 2016


Package: gitlab
Severity: wishlist

Hi,

supposedly, gitlab can be operated behind an SSL terminating reverse
proxy (I'm using pound) by adding the headers:

    X-Forwarded-Proto: https
    X-Forwarded-Ssl: on

This also works for the most part but there is still one remaining bug.
The clone URL starts with http:// even though it should be https://.
Thus, whenever I share the clone url, I now must manually replace the
http:// with a https:// which is inconvenient.

Online instructions of how to fix this problem do not seem to apply to
the Debian package as I am unable to find the referenced configuration
values. The instructions seem to be very specific to the omnibus
package.

It would be greatly appreciated if the Debian gitlab package could be
operated behind an SSL terminating reverse proxy just as easily and
without the clone-url bug.

Thanks!

cheers, josch



More information about the Pkg-ruby-extras-maintainers mailing list