Certificate for www, subdomains and wildcard

www

The name with www is automatically included in the certificate, as long as it points to your package. At WebOké, it does so by default, via the record with the asterisk in your DNS. Does https://yourdomain.nl work, but not https://www.yourdomain.nl? Then check whether www in your DNS points to a different server (see Adding or changing an A or AAAA record).

Subdomains

If you create a subdomain in Subdomain Management (see Creating and deleting subdomains), DirectAdmin also requests a certificate for it, as soon as the subdomain points to the server. This happens during the next automatic round, within 24 hours. If you don't want to wait, click Provision now in SSL/TLS Certificates (see Requesting a free Let's Encrypt certificate).

Do you see a certificate on the subdomain in the server's name (such as linux2023.webawere.nl), or a message saying the name is incorrect? Then the subdomain doesn't have its own certificate yet. Check that the subdomain points to us in the DNS, and request the certificate again.

Domain pointers

A domain pointer (see Domain pointers: a second domain name for the same site) also gets a place in the certificate, if the pointer's domain points to your package.

Wildcard

A wildcard certificate covers all subdomains at once: *.yourdomain.nl. In ACME Settings, you'll find the Prefer wildcard certificates toggle. If this is switched on, DirectAdmin tries to obtain a single wildcard certificate for your domain and all its subdomains. If that doesn't work, it requests a certificate with the individual names instead.

A wildcard is only possible if your domain's DNS is managed by WebOké (nameservers ns1.webawere.nl and ns2.webawere.nl). This is because Let's Encrypt verifies a wildcard using a temporary record in your DNS (_acme-challenge). If your DNS is managed by another provider, such as Cloudflare, DirectAdmin will place that record in the wrong location and the request will fail. In that case, switch the toggle off: you'll then get a certificate with the individual names instead, which works just as well.

Adding a custom name

With a custom or self-signed certificate, you choose the names yourself. Click the three dots after a name under DNS names without TLS certificate.

A self-signed certificate does encrypt your traffic, but browsers don't trust it and will show a warning. Only use it for testing purposes.