Update alsprolog.com to use secure HTTPS

[chuckhoupt]

I believe this involves updating DNS settings and throwing some Github switches:

https://help.github.com/articles/securing-your-github-pages-site-with-https/

[kenbowen]

On Aug 22, 2018, at 7:16 AM, Chuck Houpt notifications@github.com wrote:

Assigned #126 to @kenbowen.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or mute the thread.

Chuck,

So, it seems a little problematical [but see E) at the bottom first — think I’ve got it there]:

A) Enforcing HTTPS for your GitHub Pages site

• On GitHub, navigate to the main page of the repository.

• Under your repository name, click  Settings.

• Under "GitHub Pages," select Enforce HTTPS.

B) Under Settings for GitHub Pages:

GitHub Pages GitHub Pages is designed to host your personal, organization, or project pages from a GitHub repository.

The custom domain for your GitHub Pages site is pointed at an outdated IP address. You must update your site's DNS records if you'd like it to be available via your custom domain. For more information, see https://help.github.com/articles/setting-up-a-custom-domain-with-github-pages/. • Source Your GitHub Pages site is currently being built from the gh-pages branch. Learn more.

gh-pages branch Save Theme Chooser Select a theme to publish your site with a Jekyll theme. Learn more.

Choose a theme • Custom domain Custom domains allow you to serve your site from a domain other than appliedlogicsystems.github.io.Learn more.

Save • Enforce HTTPS — Unavailable for your site because your domain is not properly configured to support HTTPS (alsprolog.com) — Troubleshooting custom domains HTTPS provides a layer of encryption that prevents others from snooping on or tampering with traffic to your site. When HTTPS is enforced, your site will only be served over HTTPS. Learn more.

[Enforce HTTPS is grayed out]

C) On https://help.github.com/articles/setting-up-a-custom-domain-with-github-pages/. — under Setting up an apex domain, item 2:

Follow your DNS provider's instructions to create A records that point your custom domain to the following IP addresses:

• 185.199.108.153
• 185.199.109.153
• 185.199.110.153
• 185.199.111.153

I need to do A records because as far as I can see, DreamHost only has A records.

D) Current DNS records for alsprolog.com on DreamHost (except MX)

Editable: A 192.30.252.153
A 192.30.252.154
TXT google-site-verification=XXXXXXXXXXXXXXXXXX
www A 192.30.252.153
www A 192.30.252.154:

Non-editable:

    NS  ns1.dreamhost.com.
    NS  ns2.dreamhost.com.
    NS  ns3.dreamhost.com.

dev A 69.163.161.99 ftp.dev A 69.163.161.99 ssh.dev A 69.163.161.99 www.dev A 69.163.161.99

——— E) At first, I assumed the 192.30.252.153,154 IPs are something with google, because of the TXT record, but then I looked up 192.30.252.153 on https://www.infobyip.com/, and get that it’s a GitHub item:

Domain lb-192-30-252-153-iad.github.com ISP GitHub, Inc. ASN AS36459

So, should I just delete the 192.30.252.153,154 A records from DreamHost, and replace them with the 185.199.108[…].153 A records, for both apex (alsprolog.com) and www.alsprolog.com? And then presumably, the [Enforce HTTPS won’t be grayed out].

——Ken

[chuckhoupt]

Yeah, you'll have to update the A records. The https announcement post mentions the issue (meant to link in issue, but forgot):

https://blog.github.com/2018-05-01-github-pages-custom-domains-https/

If you are using A records, you must update your site’s DNS records with new IP addresses. Please see our guide to setting up your custom domain with Pages and update any A records you might have set.

[kenbowen]

Ok, got the DH A records changed. GH now says (checkbox grayed out):

Enforce HTTPS — Not yet available for your site because the certificate has not finished being issued. Please allow 24 hours for this process to complete. (alsprolog.com)

On Aug 23, 2018, at 5:43 PM, Chuck Houpt notifications@github.com wrote:

https://blog.github.com/2018-05-01-github-pages-custom-domains-https/

[kenbowen]

Done.