Very soon, Chrome and Firefox will be displaying warnings on non-SSL pages where there are input fields. Seems like this is an ideal solution for letsencrypt, but isn't it true that each cert has to have it's own IP address? I suppose that when you are creating the letsencrypt cert you could identify every subdomain used for that particular domain (I've got one domain with 15 legitimate subdomains), but what about if one of the sites is actually a true payment/transaction site which already has a commercial "seal"ed cert installed on it? And then, what happens when we add a 16th site that needs a cert? Get a whole new cert from letsencrypt that includes all 16 listed?
I mean, short of setting up each site with it's own public IP address...
And yes, I know that letsencrypt will be issuing wildcard certs starting in January of 2018. But that's 4 months away, and the warnings start in October.
Seems like with Virtualmin being great at handling virtual hosting, and letsencrypt being integrated into it, this would have come up already. But I've searched the forum and not found the question even asked.
Any direction would be appreciated.