diff options
| author | Raphael Das Gupta <raphael.das.gupta@hsr.ch> | 2019-04-10 15:02:58 +0000 |
|---|---|---|
| committer | Nick Thomas <nick@gitlab.com> | 2019-04-10 15:02:58 +0000 |
| commit | b7529f2a590bc1ded32e16592159043a7eac9ed9 (patch) | |
| tree | 1c67e0836632957d24c4964f853cf100db53e341 | |
| parent | 6febe6634277a2aae0486a6d703b160ac4333438 (diff) | |
| download | gitlab-ce-b7529f2a590bc1ded32e16592159043a7eac9ed9.tar.gz | |
Change reason for waiting
Apparently one has to wait, but DNS can't be involved at this step. (As the DNS records had already to be ready and presumably propagated for the ACME challenge to work.) So let's assume it's the content delivery network serving the certificate that needs some time here.
| -rw-r--r-- | doc/user/project/pages/lets_encrypt_for_gitlab_pages.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/project/pages/lets_encrypt_for_gitlab_pages.md b/doc/user/project/pages/lets_encrypt_for_gitlab_pages.md index 5ad500c4d20..ea22f3e905b 100644 --- a/doc/user/project/pages/lets_encrypt_for_gitlab_pages.md +++ b/doc/user/project/pages/lets_encrypt_for_gitlab_pages.md @@ -141,7 +141,7 @@ Now that your certificate has been issued, let's add it to your Pages site: ``` 1. Click **Save changes** to apply them to your website. -1. Wait a few minutes for DNS propagation. +1. Wait a few minutes for the configuration changes to take effect. 1. Visit your website at `https://example.com`. To force `https` connections on your site, navigate to your |