Hi everyone,
I’d like to setup my own Gitlab EE server with the prebuilt app from Digital Ocean served with HTTPS. The application works but I can’t get it to use the Let’s Encrypt certificate created in the DigitalOcean Security section.
The used certificate is apparently signed by me and therefore triggers a “The connection to this website isn’t secure” on the browser.
My configuration on Gitlab is the following:
nginx['redirect_http_to_https'] = true
nginx['ssl_certificate'] = "/etc/gitlab/ssl/git.domain.tld.crt"
nginx['ssl_certificate_key'] = "/etc/gitlab/ssl/git.domain.tld.key"
external_url "https://git.domain.tld"
Do you see what I’m doing wrong here?
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!
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.
Sign up for Infrastructure as a Newsletter.
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Hello,
With a self-signed SSL you would always be getting a warning. What I would suggest instead is using Let’s Encrypt. As the GitLab one-click installation uses Nginx, here’s how you could install Let’s Encrypt for Nginx:
https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04
Hope that this helps! Regards, Bobby