new acme ssl system insufficient for handling domain name changes

[digignosis]

From the 1.706 release notes: "The Evolution skin in this release supports only using the new ACME system."

So in the next release the other options will be back? I know they're available in the old skin, but this is just needlessly erasing much needed and unique functionality, without a viable replacement.

Here's a problem for instance: when changing a domain name via Domains > Rename domain, I'll need a new certificate, since the domain name has changed. I delete the old certificate (since it's the wrong domain name), turn on ACME, and press "Provision now".... still waiting after 14 hours, spinner spinning, and the "provision now" button stays greyed out. And there's no options to manage this otherwise.

I used to be able to simply select certificate domains (like domain.com and www.domain.com) for lets encrypt, press "save" and I'd have new, working certificate literally in 3 to 15 seconds (!)

And this is very necessary when planning domain name changes or website transfers. Please restore the professional options to handle lets encrypt certificates directly (and quickly), it can't be too much work I assume, since it's a skin-only issue.

Thank you, very much, for looking into this.

 

[sewiti]

From the 1.706 release notes: "The Evolution skin in this release supports only using the new ACME system."

So in the next release the other options will be back? I know they're available in the old skin, but this is just needlessly erasing much needed and unique functionality, without a viable replacement.

Here's a problem for instance: when changing a domain name via Domains > Rename domain, I'll need a new certificate, since the domain name has changed. I delete the old certificate (since it's the wrong domain name), turn on ACME, and press "Provision now".... still waiting after 14 hours, spinner spinning, and the "provision now" button stays greyed out. And there's no options to manage this otherwise.

I used to be able to simply select certificate domains (like domain.com and www.domain.com) for lets encrypt, press "save" and I'd have new, working certificate literally in 3 to 15 seconds (!)

And this is very necessary when planning domain name changes or website transfers. Please restore the professional options to handle lets encrypt certificates directly (and quickly), it can't be too much work I assume, since it's a skin-only issue.

Thank you, very much, for looking into this.

Could you confirm whether the ACME system is trying to issue a wildcard certificate for you, and whether that could be what's taking this long and causing the failure?
If it's failing for the wildcard certificate:
- Is the DNS zone controlled by DirectAdmin or externally?
- What DNS resolver is set up on the system where DirectAdmin is installed?

If the DNS zone is controlled externally, and DirectAdmin is set up to use local bind/named as the DNS resolver, it often confuses the ACME system into thinking it can control the DNS zone (therefore failing to issue wildcard certificates).

Proper fix is to stop using local named/bind as the DNS resolver.
An alternative quick fix would be disabling "Prefer wildcard certificates" in the ACME settings. Which forces ACME system to only use HTTP challenge.

If you have any more issues, please file a ticket so we can look into this in detail.