there's still a ssl error on the custom domain. Any help would be appreciated!

[brianek]

We are using cloudflare and namecheap.com. If you need any of the log-ins to fix this problem, just send me a text at 202 306 5602.

[DavidGinzberg]

I've banged my head against this with no luck a couple of times, but here's a little more info for anyone who wants to take a crack at it: The www subdomain (www.cleanslatedc.com) seems to be fine, it's the naked domain (cleanslatedc.com with no preceding subdomain) that's serving a GitHub cert instead of the one from CloudFlare (See image).

Happy bug hunting! (PS: I would love to learn the solution if someone finds one)

[stvnrlly]

I think that we discussed this before, but this is likely to be a DNS issue. I checked with a person with CloudFlare experience, who told me that using it with GitHub Pages requires their Flexible SSL offering. That means that the DNS A record needs to be pointed at CloudFlare, in addition to the CNAME record. Can you confirm that this is the setup?

[rdeprey]

Hi all,

One solution would be to use a server-side redirect to redirect all traffic
to cleanslatedc.com to the www.cleanslatedc.com URL instead. I think that
would resolve the certificate error. Here's a link to more information:
https://www.sslshopper.com/ssl-certificate-name-mismatch-error.html

Rebecca

On Tue, Dec 8, 2015, 1:38 PM stvnrlly [email protected] wrote:

I think that we discussed this before, but this is likely to be a DNS
issue. I checked with a person with CloudFlare experience, who told me that
using it with GitHub Pages requires their Flexible SSL offering. That means
that the DNS A record needs to be pointed at CloudFlare, in addition to the
CNAME record. Can you confirm that this is the setup?

—
Reply to this email directly or view it on GitHub
#148 (comment)
.