Question

Configuring Gitlab-CE with reverse Nginx SSL proxy with examples with wildcard Let's encrypt certification.

I have wildcard certification from Let’s encrypt for *.example.com and example.com. Centos 7 running omnibus gitlab-ce. Would like to run on same server gitlab.example.com and other websites like ````example.comorblog.example.comorwww.example.com. For this use case would be better to disable bundled nginx and handle it with own nginx. However I ran into issue that no tutorial covers this comprehensively (with ssl, header, selinux, etc.). For example https://docs.gitlab.com/omnibus/settings/nginx.html#using-a-non-bundled-web-server``` where are two Notes I couldn’t complete them a) I have not /home/git/ direcorty b) don’t know how determine all those directories.

Really looking for some guide from where I can learn running multiple sites on same machine each with https (idealy just wildcard certification) on reverse proxy and integrate gitlab on same machine.

Also really handy would be which part of configuration files can be included as snippets and which not (alltough even one large config file would suffice).

My attempts are getting me 502 bad gateway because I don’t really understand the context of handling several sites.


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hello friend!

I should let you know that this is not going to feel like a trivial task by any means, and what you are looking to do will not be the easiest path to resolution. Much easier would be to run other websites on another server. GitLab is plenty resource intensive to justify not sharing a server with other tasks. With that said, if you want to continue, I can only give you a direction and not a step by step process. I cannot guarantee that updates will not conflict and cause any changes here to fail later.

The config file for the Nginx that is bundled with GitLab on our one-click image, which is serving the GitLab instance over http, is /var/opt/gitlab/nginx/conf/nginx.conf. Changes here may be removed later by gitlab-ctl.

If you run a different instance of the web server to do this task, you can at least reference that nginx.conf file to find the configurations (note the includes as well) that you would want to carry over to your new configurations, so that it would continue to load GitLab as desired.

Kind Regards, Jarland