<your-username>.gitlab.io/<your-proj
ect-name> in your browseropenssl req -new -newkey rsa:2048 -nodes -keyout <your-domain-name>.key -out <your-domain-n
ame>.csr.NA
for the ‘Organization’ and ‘Organization Unit’ fields.subdomain.ssl-certificate-host.com
*.ssl-certificate-host.com
<example-domain&g
t;.com ..csr
and .key
file in your working directory. Open the .csr
file, and copy the contents in it. It should have the header ----- BEGIN CERTIFICATE REQUEST -----
.Enter CSR
field. The page will automatically fill out the domain field on the form based on the information in the CSR.CNAME
value in your domain’s DNS settings, which we will cover later on in this guide.CNAME
record for validating ownership of the domainCNAME
record you need to set up in order to confirm ownership of the domain. Copy these values to an empty text file as you’ll need to go to the ‘Advanced DNS’ page for your domain. This is accessible through ‘Dashboard’ or ‘Domain List’ > ‘Manage’ (besides your domain in the list) > ‘Advanced DNS’.<your-custom-domain&g
t;.com at the end of the ‘host’ value and you’ll be good to go.<your-username>.gitlab.io/<your
-project> when they enter <your-cus
tom-domain>.com.example.com
(or www.example.com
), so you’ll want to add the following host records:A Record
, Host @
, Value 35.185.44.232
(this is the current GitLab Pages IP at the time of writing)CNAME Record
, Host www
, Value example.com
(this ensures that people who enter the 'www’ subdomain (i.e: www.example.com
) still reach your site)TXT Record
, Host @
, Value gitlab-pages-verification-code=11112222aaaabbbb
example.com
) in the domain field, and then the next part is where it gets interesting.example_com.crt
) and your private key (generated when you initially sent the certificate request) in the fields, you’ll likely get a ‘Certificate is missing intermediates’ error.example_com.crt
and example_com.ca-bundle
files in the ‘certificate field’. In the end you should have something like: