cbor.io is accessible via HTTPS but the cert isn't right (github.io issue)

[durka]

Chrome throws up a security warning because the SSL certificate for cbor.io is registered to a.ssl.fastly.net.

[shoeper]

cbor.io is a Github Page. Not sure if it is possible to either upload a propriate certificate or disable SSL for the page.

[cabo]

Right. I could cloudflare the page, but then I'm not sure what the point of HTTPS access to the information here is in the first place.

[durka]

Yeah, I'll send a PR to the linking page instead.

…

On Tue, Apr 4, 2017 at 3:43 PM, cabo ***@***.***> wrote: Right. I could cloudflare the page, but then I'm not sure what the point of HTTPS access to the information here is in the first place. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#29 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAC3n0s5RuOVQ_vewwJRND5_utzpC4Fgks5rsp1HgaJpZM4MySen> .

[lgarron]

GitHub Pages now supports HTTPS directly: https://blog.github.com/2018-05-01-github-pages-custom-domains-https/

Would it be possible to turn this on now? :-D

[lgarron]

Ahoy! It seems that cbor.io doesn't have an automatically provisioned certificate because it's pointing at old Pages IPs:

> dig -t A cbor.io
...
cbor.io.    300 IN  A 192.30.252.154
cbor.io.    300 IN  A 192.30.252.153

Could you either replace this with a CNAME entry of cbor.github.io, or update the set of A records to the four IP addresses listed at https://help.github.com/articles/setting-up-an-apex-domain/#configuring-a-records-with-your-dns-provider ? That should fix it!

[lgarron]

@cabo: Any chance you'd be able to change the DNS records as above?

[cabo]

Will look at it this weekend. I'd love to know why people think this is a good use of my time.

[KOLANICH]

Try disabling and then enabling TLS in GH-pages settings first. For some projects it had helped.

[JeremyRand]

Any news on this?

[cabo]

I have changed the DNS records as advised by github, but I'm now traveling, so may not be able to execute further steps until later.

[lgarron]

FWIW, HTTPS is working now!

I would recommend the "Force HTTPS" setting and then call it a day for now. :-D

[cabo]

Works for me, too. Thanks for nudging me. Closing ticket now.