From: Jamie C. <jca...@we...> - 2010-12-23 21:19:07
|
On 23/Dec/2010 12:22 Danny Löser <li...@da...> wrote .. > Am 23.12.2010 20:42, schrieb Cecil Yother, Jr.: > > On 12/23/2010 11:33 AM, Danny Löser wrote: > >> Am 23.12.2010 20:08, schrieb Cecil Yother, Jr.: > >>> On 12/23/2010 10:52 AM, Danny Löser wrote: > >>>> If I change the URL without the https:// type, then I get an error > >>>> page with: > >>>> This connection is not trusted > >>>> You have Firefox instructed a secure connection to > >>>> www2.localdomain:10000 build, it can not verify that the connection > >>>> is secure. > >>>> What can I do that I get it to the https page? > >>> You need to accept the certificate. > >>> > >> No, this is it not. This is an official Comodo certificate, which is > >> under the correct domain. However, it is the wrong domain called. The > >> question is now why the call of https://domain.tld is a different > >> domain is called than if domain.tld without https is called? Was that > >> clear enough? I know my English is not good. Sorry > > > Someone else will have to chime in on this for exact details, but I > > believe you'll need to point Webmin to the Comodo certificate. > > If you think that I should tell Webmin where the certificate is, I've > had. That can it so not be. Make sure that at Webmin -> Webmin Configuration -> SSL Encryption you enter the path(s) to your comodo cert and key. Just because Apache is configured to use them, Webmin won't necessarily unless you make that change.. - Jamie |