When will it be available on In-Browser Certificate Generators?
How to issue ACMEv2 Wildcard with Certbot 0.22.0?
How to install wildcard ssl for my wpengine multisite install
The author of gethttpsforfree.com plans to add support in a couple weeks:
Please follow these issues for the latest.
Just wanted to confirm that ZeroSSL should be getting wildcards support in the SSL Certificate Wizard soon enough, now that downloadable client versions have been updated
However, it seems that even if the code gets released now, it will break on 29th of March, when the API change described as “breaking” is going to be deployed. The change introduces a requirement on the POST requests to have a specific Content-Type. Setting that type from within a browser would require the server to “confirm” in the response to a pre-flight request that it is allowed (via Access-Control-Allow-Headers). It does not seem that ACME v2 staging endpoint is configured to respond with that.
Not sure if that is a bug or that header will be coming to the staging environment “in one go” with the content-type change, but it would be nice to deploy the header some time in advance (and in all environments maybe) - so there would be no need to rush with altering clients too close to that deployment date.
Perhaps @cpu knows more about this?
Hi @leader, congrats on getting ZeroSSL to support ACMEv2
Access-Control-Allow-Headers exception for
Content-Type was raised in https://github.com/letsencrypt/boulder/issues/3554 and fixed in Boulder master. This commit will be included in tomorrow’s staging update and should be in production two days after that.
That should leave a full week to ensure there won’t be any problems ahead of the March 29th change. We can of course revisit that date if unexpected problems crop up.
Brilliant, good to know, thanks
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.