Confirm SSL management is available for the domain. Check authoritative DNS, both A and AAAA records, any proxy and CAA restrictions. Record the current certificate and ensure the requested aliases or subdomains actually exist and are intended to serve this website.

1. Open the domain SSL Certificates tool in Evolution. Choose the supported automatic or ACME certificate request option offered by the server.
2. Select only the required hostnames. Include www or mail-related names only when their DNS and service use match the request.
3. For wildcard coverage, use the supported DNS-validation arrangement and confirm who updates the authoritative DNS. An ordinary HTTP challenge cannot validate a wildcard name.
4. Submit the request and read the result. Confirm the resulting certificate is selected for the website, then enable the intended secure redirect after HTTPS has been tested.
5. Review renewal status and keep validation requirements available. If using automatic best-match certificate selection, verify which certificate is actually served to clients.

Test every requested hostname over HTTPS and inspect names, chain and expiry. Check application assets for mixed content and confirm protected pages still work. Monitor renewal rather than assuming the initial successful issuance guarantees all future renewals.

For failure, inspect the specific ACME message, public DNS, IPv6, proxy routing and CAA. Avoid repeated blind requests that can trigger issuance limits. Do not publish a private key or disable certificate verification in client applications. Preserve a currently valid certificate until the replacement is verified.

• Securing the DirectAdmin server hostname
• Troubleshooting DNS changes that do not appear from DirectAdmin
• Signing a DirectAdmin DNS zone with DNSSEC
• Adding a PHP extension through DirectAdmin CustomBuild

• DirectAdmin: SSL And Letsencrypt For Domains
• DirectAdmin: Troubleshooting Letsencrypt