<div dir="auto"><div>Not sure, perhaps there was some change on Cloudflare's side recently. In case it's helpful, my "Crypto" configuration is here: <a href="https://www.dropbox.com/s/di47zjxp38yw0ar/Crypto_Cloudflare.pdf?dl=0">https://www.dropbox.com/s/di47zjxp38yw0ar/Crypto_Cloudflare.pdf?dl=0</a></div><div dir="auto"><br></div><div dir="auto">My personal site is similarly hosted with ghpages, and I set Cloudflare up about a month ago. HTTPS redirection seems to work ok (try <a href="http://shyam.saladi.org">http://shyam.saladi.org</a>)</div><div dir="auto"><br></div><div dir="auto">Shyam<br><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">On Sep 14, 2017 5:45 PM, "Hilmar Lapp" <<a href="mailto:hlapp@drycafe.net">hlapp@drycafe.net</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">I thought activating that option required HTTPS and a valid SSL cert on the source site too. At least that’s what it seemed to be recently when I tried that (with my own website, also currently hosted off of Github Pages).<font color="#888888"><div><br></div><div> -hilmar</div></font><div><div class="elided-text"><br><div><blockquote type="cite"><div>On Sep 14, 2017, at 8:10 PM, Shyam Saladi <<a href="mailto:saladi1@illinois.edu" target="_blank">saladi1@illinois.edu</a>> wrote:</div><br class="m_-6604650674066858985Apple-interchange-newline"><div><div dir="ltr"><div>A minor point, but I think that Cloudflare can redirect http to https:</div><div><br></div><div><a href="https://support.cloudflare.com/hc/en-us/articles/200170536-How-do-I-redirect-all-visitors-to-HTTPS-SSL-" target="_blank">https://support.cloudflare.<wbr>com/hc/en-us/articles/<wbr>200170536-How-do-I-redirect-<wbr>all-visitors-to-HTTPS-SSL-</a><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 14, 2017 at 3:18 PM, Hilmar Lapp <span dir="ltr"><<a href="mailto:hlapp@drycafe.net" target="_blank">hlapp@drycafe.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Not directly, that's correct. However, there are at least three alternatives, each with various pros and cons.<br>
<br>
1) We could front the site with Cloudflare. This would give us a free SSL cert from Cloudflare. It would not redirect http to https, and would require moving DNS for the domain to Cloudflare.<br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
2) Proxy the traffic from <a href="http://github.io" target="_blank">Github.io</a> through our Apache server on AWS. This would allow us to redirect http to https, and we'd use a Let's Encrypt SSL cert. For Apache the LE certbot can auto-renew, I think. In essence this is us doing some of what Cloudflare would do, except for DDOS protection, so the site would then have a single point of failure.<br>
<br>
3) Use Gitlab Pages for hosting. This would allow SSL certs for custom domains. My understanding is they also support Let's Encrypt for cert renewal, but I haven't tried that yet. Downside is that now we're hosting the repo in a different place than everything else Bioperl. I also don't know about redirecting http to https.<br>
<br>
-hilmar<br>
<br>
Sent from away<br>
<div class="m_-6604650674066858985gmail-HOEnZb"><div class="m_-6604650674066858985gmail-h5"><br>
> On Sep 14, 2017, at 5:42 PM, Peter Cock <<a href="mailto:p.j.a.cock@googlemail.com" target="_blank">p.j.a.cock@googlemail.com</a>> wrote:<br>
><br>
> As far as I know, using your own domain with<br>
> GitHub pages and HTTPS is still not possible.<br>
><br>
> Peter<br>
><br>
>> On Thu, Sep 14, 2017 at 6:10 PM, Carnë Draug <<a href="mailto:carandraug%2Bdev@gmail.com" target="_blank">carandraug+dev@gmail.com</a>> wrote:<br>
>> Hi<br>
>><br>
>> If you access <a href="https://bioperl.org/" rel="noreferrer" target="_blank">https://bioperl.org</a> you will get a SSL_ERROR_BAD_CERT_DOMAIN<br>
>><br>
>> The problem is that current certificate is only valid for <a href="http://github.io/" rel="noreferrer" target="_blank">github.io</a><br>
>> domains.<br>
>><br>
>> Carnë<br>
>><br>
>> ______________________________<wbr>_________________<br>
>> Bioperl-l mailing list<br>
>> <a href="mailto:Bioperl-l@mailman.open-bio.org" target="_blank">Bioperl-l@mailman.open-bio.org</a><br>
>> <a href="http://mailman.open-bio.org/mailman/listinfo/bioperl-l" rel="noreferrer" target="_blank">http://mailman.open-bio.org/ma<wbr>ilman/listinfo/bioperl-l</a><br>
><br>
> ______________________________<wbr>_________________<br>
> Bioperl-l mailing list<br>
> <a href="mailto:Bioperl-l@mailman.open-bio.org" target="_blank">Bioperl-l@mailman.open-bio.org</a><br>
> <a href="http://mailman.open-bio.org/mailman/listinfo/bioperl-l" rel="noreferrer" target="_blank">http://mailman.open-bio.org/ma<wbr>ilman/listinfo/bioperl-l</a><br>
<br>
______________________________<wbr>_________________<br>
Bioperl-l mailing list<br>
<a href="mailto:Bioperl-l@mailman.open-bio.org" target="_blank">Bioperl-l@mailman.open-bio.org</a><br>
<a href="http://mailman.open-bio.org/mailman/listinfo/bioperl-l" rel="noreferrer" target="_blank">http://mailman.open-bio.org/ma<wbr>ilman/listinfo/bioperl-l</a></div></div></blockquote></div><br></div></div>
</div></blockquote></div><br></div><div class="quoted-text"><div>
<div><div style="font-family:Monaco;font-size:11px">-- </div><div style="font-family:Monaco;font-size:11px">Hilmar Lapp -:- <a href="http://lappland.io" target="_blank">lappland.io</a></div></div><div><br></div><br class="m_-6604650674066858985Apple-interchange-newline">
</div>
<br></div></div></div></blockquote></div><br></div></div></div>