This question had been asked again & again in this forum. but the answer to that previously was that it was very tedious and cumbersome process to set things as previous Letsencrypt didn’t issue Wildcard certificates.
But now Letsencrypt has officially launched Wildcard certificates and is available for public testing.
My question is will easy engine support Wildcard certificate issuing, because now letsencrpyt supports it now?
What are the things that would be needed to alter or modified so that it EE supports that functionality.
PS: Need EE to support Letsencrypt for Multiple domains on a single server, but that was not possible earlier, hence i used to take up multiple small aws servers rather than a big server.
So if EE was to support Letsencrypt and multiple domain setup; we could easily use a dedicated CDN with cloudflare enable at full SSL.
User Case: I was able to use AWS Cloudfront + Cloudflare on the first domain that was installed via EE and letencrypt; however later installed multiple domains but they all had the first domain ssl enabled while detected using curl.
Normally they(sites) all work fine, but with cdn trying to get pull data, due to https validation for certs, sites tell those cdns that my site are using invalid letsencrypt ssl cert, so they have arent able to reach the origin.
However the site 1 work all well.
Summarizing, with introduction of multiple domain and subdomain letsencrypt support for EE can really benefit a lot of people.