Thanks Michael, Do you have a working instance with a self signed cert? With local IP or <hostname>.localhost in cert. And your browser is happy with singing.
Have tried Chrome/Firefox/Chromium. On Wednesday, August 24, 2016 at 3:51:09 PM UTC+1, Michael Hofer wrote: > > Hi > > On Wed, 24 Aug 2016 07:45:54 -0700 (PDT) > [email protected] <javascript:> wrote: > > Thanks Chris, > > > > Yes that will get me passed having to click through the warning but will > > not get rid of the broken lock. > > > > Since it is a local server it does not have a public domain name. There > for > > i cannot get a cert from a CA, it needs to be a self signed cert. > > > > Just wondering if anyone has experience deploying Foreman over https > > locally. > [...] > > If you actually properly import the certificate into your browser you > should no > longer see any broken lock. What browser are you using? Chrome for > example displays a broken lock for certificates with SHA1 hashes. > > Cheers > > Michael > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
