IPv6 support

[ikomwrestling]

Describe the bug
momentjs.com lacks IPv6 addresses and thus resources (JavaScript) from it can't be received using IPv6.

Since the CDN seems to be served by Cloudflare, which has great IPv6 support, it should hopefully be a simple fix by enable IPv6 in dashboard, as per their IPv6 documentation.

Thank you.

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Chrome
• Version 90

[marwahaha]

Which CDN are you using?

[Krinkle]

Hi. I'm a volunteer on the OpenJS Infrastructure team (mainly for jQuery and other former jQuery Foundation projects). According to the Cloudflare configuration, IPv6 was enabled for momentjs.com domains 7 years ago.

$ host momentjs.com
momentjs.com has address 104.16.153.25
momentjs.com has address 104.17.93.38
momentjs.com has IPv6 address 2606:4700::6811:5d26
momentjs.com has IPv6 address 2606:4700::6810:9919

$ curl -v -6 -I https://momentjs.com
…
* Connected to momentjs.com (2606:4700::6810:9919) port 443
* …
> HEAD / HTTP/2
> Host: momentjs.com
> User-Agent: curl/8.2.1
> Accept: */*
> 
< HTTP/2 200 

I note that GitHub themselves also use a CDN (Fastly) and that too supports IPv6 already.

$ host moment.github.io
moment.github.io has address 185.199.109.153
moment.github.io has address 185.199.108.153
moment.github.io has address 185.199.110.153
moment.github.io has address 185.199.111.153
moment.github.io has IPv6 address 2606:50c0:8000::153
moment.github.io has IPv6 address 2606:50c0:8001::153
moment.github.io has IPv6 address 2606:50c0:8002::153
moment.github.io has IPv6 address 2606:50c0:8003::153

Maybe we don't need the double layered CDN here?

It looks like GitHub isn't currently trying to provision a Let's Encrypt certificate for this domain so I can't actually turn this off.

@gilmoreorless @ichernev Do one of you have admin access on this repo to check the Pages settings? Maybe there's a domain verification or HTTPS setting that needs to be initiated.

[gilmoreorless]

Thanks for looking into this @Krinkle.

The GitHub Pages setting for this repo has the "Enforce HTTPS" checkbox disabled, with the message:

Unavailable for your site because your domain is not properly configured to support HTTPS (momentjs.com) — Troubleshooting custom domains

[Krinkle]

@gilmoreorless Okay, I've follow the CNAME/ALIAS instructions. The site is now served with missing certificate.

It's a bit annoying that to fix enforcement of HTTPS we actually have to temporary break all HTTPS. But, I guess that's how it works with GitHub Pages?

From https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages#https-errors

It can take up to an hour […]. After you update existing DNS settings, you may need to remove and re-add your custom domain to your site's repository to trigger the process of enabling HTTPS. […]

I guess that's worth a try at https://github.com/moment/momentjs.com/settings. I'll give it an hour or so before reverting. You can also ping me through various methods.

[Krinkle]

I've re-enabled Cloudflare proxy with the old DNS settings.