Command-line tool to generate a Let's Encrypt certificate for use with GitLab Pages.
npm install -g gitlab-letsencryptgitlab-le \
--email [email protected] `# REQUIRED - Let's Encrypt email address` \
--domain example.com www.example.com `# REQUIRED - Domain(s) that the cert will be issued for (separated by spaces)` \
--repository gitlab_user/gitlab_repo `# REQUIRED - Namespaced repository identifier` \
--token ... `# REQUIRED - GitLab personal access token, see https://gitlab.com/profile/personal_access_tokens` \
--jekyll `# OPTIONAL - Upload challenge files with a Jekyll-compatible YAML front matter` \
--path `# OPTIONAL - Absolute path in your repository where challenge files should be uploaded`See gitlab-le --help for more details.
$ gitlab-le --jekyll --path / --email [email protected] --repository example/example.gitlab.io --token ... --domain example.com www.example.com
By using Let's Encrypt, you are agreeing to the TOS at https://letsencrypt.org/documents/LE-SA-v1.0.1-July-27-2015.pdf
Uploaded challenge file, waiting for it to be available at http://example.com/.well-known/acme-challenge/lLqa_7sLPQzz102c2KIc3pqMevUyM_Ru92whx6w1C-4
Could not find challenge file. Retrying in 15s...
Could not find challenge file. Retrying in 30s...
Could not find challenge file. Retrying in 1m...
Success! Go to https://gitlab.com/example/example.gitlab.io/pages and create/re-create domain(s) with the following settings:
Domain(s): example.com, www.example.com
Certificate (PEM):
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
Key (PEM):
-----BEGIN RSA PRIVATE KEY-----
...
-----END RSA PRIVATE KEY-----
This certificate expires on Sat Aug 26 2017 18:27:00 GMT-0300 (-03). You will need to repeat these steps at some time before this date.
If you'd like to improve this situation, please join the discussion at https://gitlab.com/gitlab-org/gitlab-ce/issues/28996
- Requests a challenge from Let's Encrypt using the provided email address for the specified domains. One challenge file is generated per domain
- Each challenge file is uploaded to your GitLab repository using GitLab's API, which commits to your repository
- The challenge URL is repeatedly polled until the challenge file is made available. GitLab Pages take a while to update after changes are committed
- If Let's Encrypt was able to verify the challenge file, a certificate for that domain is issued
- Each challenge file is removed from your GitLab repository by committing to it through the GitLab API
Because Let's Encrypt is a fully automated certificate authority, all issued certificates expire in 90 days.
A fresh certificate can be obtained at any time by running gitlab-le again, as long as you are within Let's Encrypt's rate limits.
If you want to test that your GitLab Page is configured correctly for use with gitlab-le, you can use the --staging option to use Let's Encrypt's staging environment.
The staging environment has a virtually infinite rate limit for obtaining certificates, but it will issue dummy certificates that should not be trusted.
gitlab-le does not save or log anything to disk.
The GitLab access token is used to upload the challenge file to your repository and to delete it once the challenge is completed.
Even though challenge files are deleted from your repository after a challenge file is deleted, they are still visible in the repository's commit history. In any case, challenge files do not have any value after a challenge has been completed, so this is not a security risk.
Let's Encrypt certificates expire every 90 days - this is by design to take advantage of automated renewals using ACME. However, GitLab does not provide a way to automatically renew certificates, so this process must be done manually.
GitLab does not provide an API to update domains or certificates for a Page, so these must be updated manually through the UI. If you like this tool and want full automation (e.g. stick this in a cron job and forget about it), let GitLab know!