Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save mquan/f20ca1875cedeb1fa288 to your computer and use it in GitHub Desktop.
Save mquan/f20ca1875cedeb1fa288 to your computer and use it in GitHub Desktop.
Github Pages: Let's Encrypt!

Please petition Github to support HTTPS on github pages: https://github.com/contact

Here's what I wrote:

Obviously, a lot of people want HTTPS for github pages:

Until recently, that would be difficult to implement but, as it turns out, the implementation is pretty much complete:

I'm a freelancer, so I've got time and I'd love to help out in any way I can (I'd even come work for you at a substandard rate) if we could get this implemented by Let's Encrypt launch day.

You can also send a message to support@github.com

@nubela
Copy link

nubela commented Mar 7, 2016

Full disclosure: I work at Kloudsec.

But anyways, Kloudsec solves the problem of getting custom domained Github Pages to HTTPS. See Kloudsec for Github Pages.

Kloudsec is a minimal CDN (open) platform. Because it is an open platform, we also implemented LetsEncrypt CA to auto-provision SSL if you enable the One-click Encryption plugin.

All you have to do is to update your custom domain to point to our CDN's IP address. (Unlike Cloudflare, you can keep your nameservers)


In other words, Kloudsec for Github Pages solves the 2 biggest issues with custom domains on GIthub pages:

  1. No CDN support for apex domains
  2. No HTTPS for custom domains

You also get all the other plugins for free:

  • Page Optimizer (Pagespeed optimisations)
  • Service Doctor (Performance Analytics)

We have a public Telegram chat group for Kloudsec if you need help

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