Another alternative I have used is to get a new certificate that includes all the subdomains.
Dave Copeland. On 02/05/17 06:17 PM, Martin wrote: > On 02/05/2017 22:59, Michael Van Canneyt wrote: >> >>> That's probably good as the fastest / short-term solution, but as >>> long as >>> both DNS records are valid and point to the same IP address (and http >>> access to both is redirected to the https version), the certificate >>> should >>> cover both domain names as well. >> >> That mayb be so, but I have no idea how to do this. >> As far as I know, lets encrypt does not support wildcard certificates. > > I would think you need 2 individual certs. > > Since both domains are on the same IP, the server must support SNI > (but most servers do). > > Then have 2 virtual hosts, one for each domain. Each using the correct > cert for its domain. > The rest of the virtualhosts will be a copy of each other (or > including the same include file) > _______________________________________________ > fpc-devel maillist - [email protected] > http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel -- David Copeland JSI Data Systems Limited 613-727-9353 www.jsidata.ca _______________________________________________ fpc-devel maillist - [email protected] http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
