Let's Encrypt Wildcard Integration
Let's Encrypt Integration came with UTM 9.6. That's great!
You should now implement the support of Let's Encrypt Wilcard domains with ACMEv2.
Edgar Stach commented
From now on the Lets Encrypt Registration only Works with ACMEv2
Messsage from LetsEncrypt:
fw letsencrypt: E Create account: REG_FAILED: "detail": "Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details.",
[Deleted User] commented
The Apache Software Foundation as of late discharged Hadoop 2.0 that joins a few new includes, including YARN. This discharge additionally sparkles light on a noteworthy issue that companies considering Hadoop activities are bound to confront the staggering absence of Hadoop expertise in the present work pool.
For More Info:- https://hadoop-training1.wixsite.com/hadoop-course
AdminJan Weber (Product Manager, Network Security Group, Sophos Features & Ideas Laboratory) commented
We are currently not considering adding wildcard support. The Let's Encrypt Wildcard support uses DNS TXT entries to validate domain ownership, as opposed to the HTTP file based challenge for other certificates, which is something that we can't easily automate and make it as easy to use as with the other certificates.
We do not have any control over the DNS records and hence this would require user/admin interaction for certificate generation as well as renewal.