https://www.circuitpython.org/ is insecure

[tannewt]

Going to https://www.circuitpython.org/ generates a cert warning on Firefox.

[ptorrone]

chrome too, here is some more info:
NET::ERR_CERT_COMMON_NAME_INVALID

[jwcooper]

This is currently a known issue with GitHub pages. I'll see about setting up a cloudflare redirect or something similar.

Discussion here:
https://github.community/t5/GitHub-Pages/Does-GitHub-Pages-Support-HTTPS-for-www-and-subdomains/m-p/7202#M495
isaacs/github#1675

[tannewt]

@ptorrone keep this in mind when linking to the site. I saw the www. version recently in something (can't remember what.)

[ptorrone]

@tannewt @jwcooper yep, looks like https://circuitpython.org/ is fine, so if anyone sees www somewhere and can edit, please do, otherwise let me know and i'll edit, or we'll see what we can do.

[makermelissa]

I’m not familiar with the intricacies of Github pages, but on apache-based servers, you can add a rule that will forward somebody from www.circuitpython.org <http://www.circuitpython.org/> to circuitpython.org. Likewise with http to https. Is there a way of doing that with the GitHub pages? Melissa

…

On Dec 4, 2019, at 10:47 AM, phillip torrone ***@***.***> wrote: @tannewt <https://github.com/tannewt> @jwcooper <https://github.com/jwcooper> yep, looks like https://circuitpython.org/ <https://circuitpython.org/> is fine, so if anyone sees www somewhere and can edit, please do, otherwise let me know and i'll edit, or we'll see what we can do. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#330?email_source=notifications&email_token=AAUOUSPJZ55MURCOFDQMVODQW73LFA5CNFSM4JVMTT72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF6CT6Q#issuecomment-561785338>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUOUSOZ5CVHY46BVTHWJZTQW73LFANCNFSM4JVMTT7Q>.

[jwcooper]

Unfortunately, I haven't seen any access to anything like this yet. GitHub doesn't really offer a suggested solution.

The best option I've seen is have www.circuitpython.org be setup with CloudFlare ssl and do a CloudFlare page rule to redirect it back to circuitpython.org. GitHub is using letsencrypt to create the ssl cert, and isn't creating one that's valid for www.circuitpython.org. They offer the option to do one or the other.

There is a hack to swap the cname in github settings, but you'd have to remember to do that every 3 months as the certs expire, and I'd like to avoid doing that.

[makermelissa]

@jwcooper I like your suggestion for the "best option". :)

[theacodes]

Cloudflare is your best best here, I'm happy to help set it up if needed!

[jwcooper]

We've started the process to transfer to cloudflare. Thanks for all the help everyone! We should be able to configure this once the transfer is complete.

[jwcooper]

This has been completed.

www.circuitpython.org will now 301 redirect to circuitpython.org.

[makermelissa]

Thank you @jwcooper