Re: Bad SSL certificate at bioperl.org
Hilmar Lapp <[email protected]> Thu, 14 Sep 2017 20:44:58 -0400
| Newsgroups | gmane.comp.lang.perl.bio.general |
|---|---|
| Message-ID | <[email protected]> |
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). -hilmar > On Sep 14, 2017, at 8:10 PM, Shyam Saladi <[email protected]> wrote: > > A minor point, but I think that Cloudflare can redirect http to https: > > https://support.cloudflare.com/hc/en-us/articles/200170536-How-do-I-redirect-all-visitors-to-HTTPS-SSL- <https://support.cloudflare.com/hc/en-us/articles/200170536-How-do-I-redirect-all-visitors-to-HTTPS-SSL-> > > On Thu, Sep 14, 2017 at 3:18 PM, Hilmar Lapp <[email protected] <mailto:[email protected]>> wrote: > 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 <[email protected] <mailto:[email protected]>> 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 <[email protected] <mailto:carandraug%[email protected]>> wrote: > >> Hi > >> > >> If you access https://bioperl.org <https://bioperl.org/> you will get a SSL_ERROR_BAD_CERT_DOMAIN > >> > >> The problem is that current certificate is only valid for github.io <http://github.io/> > >> domains. > >> > >> Carnë > >> > >> _______________________________________________ > >> Bioperl-l mailing list > >> [email protected] <mailto:[email protected]> > >> http://mailman.open-bio.org/mailman/listinfo/bioperl-l <http://mailman.open-bio.org/mailman/listinfo/bioperl-l> > > > > _______________________________________________ > > Bioperl-l mailing list > > [email protected] <mailto:[email protected]> > > http://mailman.open-bio.org/mailman/listinfo/bioperl-l <http://mailman.open-bio.org/mailman/listinfo/bioperl-l> > > _______________________________________________ > Bioperl-l mailing list > [email protected] <mailto:[email protected]> > http://mailman.open-bio.org/mailman/listinfo/bioperl-l <http://mailman.open-bio.org/mailman/listinfo/bioperl-l> -- Hilmar Lapp -:- lappland.io _______________________________________________ Bioperl-l mailing list [email protected] http://mailman.open-bio.org/mailman/listinfo/bioperl-l