Hi Cos, Alexey Chetaev, please join the conversation and share your thoughts on this.
— Denis > On Jul 19, 2017, at 9:44 AM, Konstantin Boudnik <c...@apache.org> wrote: > > Hey guys. > > I've noticed that https://ci.ignite.apache.org/ has two issues: > - it has the invalid certificate > - the CI server isn't responding on the https port (there's only ngnix) > > I don't about the rest of the group here, but all my browsers are enforcing > HTTPS connections for the obvious reasons. I have to add an exception > for the CI server to get in, which is a minor inconvenience compared to the > security risks. I suggest we fix both issues. > 1. Getting a valid certificate is easy and doesn't cost a dime nowadays. > Here's the very details set of instructions on how we do it for Apache > Bigtop. They are easily applicable in Ignite CI's case [1]. I'd be happy to > help with this. > 2. Reconfiguring the server to respond only on HTTPS port. That's another easy > thing to do for anyone with the access to the box. I don't have this, so > it'd be someone else. > > Thoughts? > Cos > > [1] > https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+CI+Setup+Guide#BigtopCISetupGuide-Advancedpart:SetupaSSLsecuredJenkinsmaster >
