Use HTTPS #211

Open
ai opened this Issue Jun 9, 2016 · 13 comments

Projects

None yet

4 participants

@ai
Member
ai commented Jun 9, 2016

GitHub pages supports SSL. Could we use it for custom domain?

https://github.com/blog/2186-https-for-github-pages

@marcustisater
Member

That's cool. Unfortunately it does not work on custom domains.

"HTTPS is not supported for GitHub Pages using custom domains."

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

@thangngoc89
Contributor

You guys can use Cloudflare or Kloudsec for HTTPS.

@marcustisater
Member

Ah, I didn't know that.

@ai thoughts?

@marcustisater marcustisater reopened this Jun 9, 2016
@ai
Member
ai commented Jun 9, 2016

@thangngoc89 Kloudsec looks promising. What do we need? How it works? What is the price?

@thangngoc89
Contributor
thangngoc89 commented Jun 9, 2016 edited

@ai It's currently free (Thanks to Let's encrypt) . All you need is point your domain to kloudsec. (Just follow the instruction on the page)

@marcustisater
Member

I can set it up if you would like. I have domain info.

@ai
Member
ai commented Jun 9, 2016

@marcustisater awesome, let’s try! Ping me when you will finish it.

@marcustisater
Member

will do

@marcustisater
Member

Sorry... 😓

https://kloudsec.com/ is offline. Any other tips for https?

@thangngoc89
Contributor

https://www.netlify.com
Is a full service for static page

@okonet
Collaborator
okonet commented Jan 9, 2017

Netlify is cool. I second this.

@marcustisater
Member

Agree, it works great https://public-relations-officer-claudia-65056.netlify.com/. I just need to change DNS.

@marcustisater
Member
marcustisater commented Jan 16, 2017 edited

From Netlify:

Ah, you use gandi.net (so do I - but not for DNS because of what I'm about to say). They don't support an ALIAS or ANAME or flattened CNAME record which is the best way to get full advantage of our CDN for your bare domain (vs www.postcss.org which should be the CNAME you mention).
Two suggestions, one related and one unrelated:
if you don't mind, using 'www.postcss.org' instead of 'postcss.org' for your canonical hostname - put it as the custom domain in your settings page instead of 'postcss.org' - this will work around this and your visitors will get to use the CDN (we'll 301 redirect from postcss.org -> www.postcss.org automatically so all the content will come from the CDN even though the redirect comes from our one-location load balancer)
you should upgrade yourself to the open source plan here: https://app.netlify.com/sites/public-relations-officer-claudia-65056/plan . Your site definitely is the type of site we're intending to help out with our free open source plan!
I understand if for #1 you really prefer to use 'postcss.org' instead of 'www.postcss.org' but in that case I'd recommend getting a more capable DNS provider like CloudFlare (also I think should be free for your use case) - they support CNAME flattening so you can CNAME your apex domain and still process mail and do all the normal things with that domain.

I talked to @ai and we have decided to wait with this because postcss.org domain without www prefix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment