Skip to content

Commit

Permalink
add troubleshooting ssl cert provisioning in pages (github#12030)
Browse files Browse the repository at this point in the history
* add troubleshooting ssl cert provisioning in pages

* Update content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md

Some minor rewording of the change suggested by @tcbyrd.

* Update content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md

Minor rewording.

Co-authored-by: hubwriter <[email protected]>
  • Loading branch information
dojobo and hubwriter authored Dec 21, 2021
1 parent 6ce6ba8 commit 052c0ac
Showing 1 changed file with 6 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,12 @@ All {% data variables.product.prodname_pages %} sites, including sites that are
3. Under "{% data variables.product.prodname_pages %}," select **Enforce HTTPS**.
![Enforce HTTPS checkbox](/assets/images/help/pages/enforce-https-checkbox.png)

## Troubleshooting certificate provisioning ("Certificate not yet created" error")

When you set or change your custom domain in the Pages settings, an automatic DNS check begins. This check determines if your DNS settings are configured to allow {% data variables.product.prodname_dotcom %} to obtain a certificate automatically. If the check is successful, {% data variables.product.prodname_dotcom %} queues a job to request a TLS certificate from [Let's Encrypt](https://letsencrypt.org/). On receiving receiving a valid certificate, {% data variables.product.prodname_dotcom %} automatically uploads it to the servers that handle TLS termination for Pages. When this process completes successfully, a check mark is displayed beside your custom domain name.

The process may take some time. If the process has not completed several minutes after you clicked **Save**, try clicking **Remove** next to your custom domain name. Retype the domain name and click **Save** again. This will cancel and restart the provisioning process.

## Resolving problems with mixed content

If you enable HTTPS for your {% data variables.product.prodname_pages %} site but your site's HTML still references images, CSS, or JavaScript over HTTP, then your site is serving *mixed content*. Serving mixed content may make your site less secure and cause trouble loading assets.
Expand Down

0 comments on commit 052c0ac

Please sign in to comment.