[Bioperl-l] Bad SSL certificate at bioperl.org

[Hilmar Lapp]

Not directly, that's correct.  However, there are at least three alternatives, each with various pros and cons.

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.

2) Proxy the traffic from Github.io 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.

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.

-hilmar

Sent from away

> On Sep 14, 2017, at 5:42 PM, Peter Cock <p.j.a.cock at googlemail.com> wrote:
> 
> As far as I know, using your own domain with
> GitHub pages and HTTPS is still not possible.
> 
> Peter
> 
>> On Thu, Sep 14, 2017 at 6:10 PM, Carnë Draug <carandraug+dev at gmail.com> wrote:
>> Hi
>> 
>> If you access https://bioperl.org you will get a SSL_ERROR_BAD_CERT_DOMAIN
>> 
>> The problem is that current certificate is only valid for github.io
>> domains.
>> 
>> Carnë
>> 
>> _______________________________________________
>> Bioperl-l mailing list
>> Bioperl-l at mailman.open-bio.org
>> http://mailman.open-bio.org/mailman/listinfo/bioperl-l
> 
> _______________________________________________
> Bioperl-l mailing list
> Bioperl-l at mailman.open-bio.org
> http://mailman.open-bio.org/mailman/listinfo/bioperl-l