Re: [webmin-l] Certificate Problem

[Kimberly <kim...@gm...>]

I am a little bit confused on this.  I thought let's encrypt tries to 
connect to the website on port 443 to test if there is an actual website 
there before it will issue the certificate.

On 2/24/2017 4:01 PM, Kris Deugau wrote:
> Kimberly wrote:
>> I ran all the Virtualmin package upgrades and it still reports 5.06 and
>> it still reports domain has no website when trying to request a certificate.
>> Is there another way to upgrade Virtualmin other than package updates?
>> Is this done from the command line.  Any help is appreciated.
> I haven't looked into LE yet, but I'm wondering if there's an issue due
> to the HTTP->HTTPS redirect:
>
>>>>>> virtual server.  After changing the domain name the site will load; the
>>>>>> site is redirected to the https and loads but with a warning about the
>>>>>> certificate.
> The LetsEncrypt back end may be expecting either plain HTTP, or HTTPS
> with a valid cert (right domain, not expired, etc).  wget, for instance,
> is very picky about having a completely valid cert or it won't retrieve
> whatever you've requested.
>
> I'd try disabling the HTTP->HTTPS redirect, so whatever validation blob
> is needed can be retrieved from the HTTP site.
>
> -kgd
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> -
> Forwarded by the Webmin mailing list at web...@li...
> To remove yourself from this list, go to
> http://lists.sourceforge.net/lists/listinfo/webadmin-list
>