On 12/10/2018 08.32, Per Jessen wrote:
The reason it does not work is - in comparison to http, when you are using https, you first need an encrypted connection. This can only be established if the site you are visiting can be properly identified and provided it has a certificate to match the name. For a default vhost you would need a certificate to match all the (otherwise unmatched) possible names and addresses.
For my illustration :-) You say all possible names and addresses. So if I were to set up a site on my dynamic address, it would not work, because being dynamic the address is subject to change, right? Or would be it possible to do, when the IP changes: · change the certificate on the fly · update the dns to point to the new IP This is just for learning, I do not intend to set a site for the moment :-) -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)