We previously communicated that we would launch ACMEv2 and wildcard certificate support on February 27th. ACMEv2 and wildcard support is nearly ready but we will be delaying the full launch in order to give our teams more time to complete testing and quality assurance activities. While we work hard …

Advising customers and making promises to them about solutions that are reliant on a third party provider, which is outside of your control, sounds like poor management to me. Making assumptions is what has got you to the point that you don’t have any answers. I would rather the wildcard certificat…

Almost everyone of us uses third party “provider”. And its not making promising, advising them that something is going to available soon based on the providers notes and published timeline. Its all about communication. But may be something which you will not understand. We never made any assumption…

Well, please forget about my last comment:) I really do not mean any rush to LE But I agree with other folks: please communicate community more clearly There is nothing worse than bad communication which directly leads to lack of trust I can even suggest LE to ask help from community in releasing…

Got to be right of course but the sooner the better. Thanks for the effort!

Will ACMEv2 and wildcard be available before April 4, or will I need to renew my existing non-wildcard certificates at least one more time?

There’s still a fair degree of activity on the ACME mailing list. I’m no one of influence, but if I were a betting man I’d anticipate another non-wildcard renewal.

Trust is definitely more important than hitting deadlines. As long as the issuance is waterproof and fool-proof we are happy. Way to go Let’s Encrypt

I’ve been waiting for a long time for wildcard certificates to happen, so I’m in high anticipation. A few more days/weeks of waiting wouldn’t change anything for me. I’m extremely excited that LetsEncrypt has gotten as far as it has. When it started, I was merely hopeful that it would have the means…

I notice that acme-v02.api.letsencrypt.org is resolving, responding, and serving up valid certificates… just waiting for the official announcement now. :smiley:

[image] RealDeuce: and serving up valid certificates You can get production certs from the acme-v02 endpoint right now, but wildcards are not yet enabled. Error creating new order: acme: error code 400 "urn:ietf:params:acme:error:malformed": Error creating new order :: Wildcard names not su…

ACMEv2 and Wildcard Launch Delay

Feature Requests

jurekam March 13, 2018, 5:12pm 67

Wildcard is here! See this for details:

Topic		Replies	Views
Wildcards official launch Feature Requests	2	5668	March 23, 2018
Wildcard Certificates Coming January 2018 Issuance Policy	67	18993	October 13, 2017
End of Life Plan for ACMEv1 API Announcements	27	199922	September 15, 2021
Please support wildcard certificates Issuance Policy	67	84430	October 13, 2015
Acme.sh supports ACME v2 wildcard now Client dev	60	41446	May 9, 2018

ACMEv2 and Wildcard Launch Delay

Related topics