Innovate | Connect | Transform
ContactService statusUSD $

GICT knowledge base

Install a Website TLS Certificate in DirectAdmin

Published

SSLDirectAdmin

For a DirectAdmin website, choose either supported automatic certificate management or installation of an issued certificate with its matching key. A shared-server or self-signed selection does not by itself prove that visitors receive a trusted certificate for your domain.

Prepare the domain

Confirm the correct user/domain, public DNS and required hostnames. Keep the current certificate configuration recoverable. In User Level, open SSL Certificates; menu labels vary by skin/version. Server-hostname certificates have a separate administrator workflow.

Automatic issuance

If enabled by the administrator, use the domain’s ACME settings and select the names you actually need. Review validation failures before retrying. Wildcard requests require an appropriate DNS-validation route; secure DNS API credentials with the narrowest supported access. Do not assume adding a domain to the request establishes coverage.

Install an existing certificate

  1. Choose the certificate/key installation option for the intended domain.
  2. Supply the issued certificate and its matching private key through the trusted panel. Do not create a new unrelated key after the certificate has been issued.
  3. Provide the issuer’s intermediate chain in the appropriate chain/CA field. Keep certificate, key and chain roles distinct.
  4. Save, inspect the result and test each public hostname without bypassing warnings.

Check the actual certificate presented through any CDN as well as the origin configuration. Confirm expiry monitoring and who renews it. Installing a certificate does not automatically fix HTTP application URLs, mixed content or a separate mail endpoint.

References: DirectAdmin domain ACME management; DirectAdmin TLS documentation.

Reviewed October 15, 2026. No DirectAdmin account, DNS credential or live certificate was changed.

Related guides

Account services are unavailable until the production backend is configured.