If you searched for “install ssl directadmin”, the practical process is to point your domain to the hosting account, request a free Let’s Encrypt certificate, and then turn on the HTTPS redirect. The complete process normally takes a few minutes when the domain, www, and any selected mail hostname already resolve to the correct hosting account.
This guide is for a normal domain hosted in DirectAdmin. Replace example.com with your own domain in every example. The exact labels can differ slightly between DirectAdmin skins, but the SSL page and the steps are the same.
Before opening DirectAdmin, keep these details ready:
example.com or www.example.com.HostKarle’s DirectAdmin plans include a free auto-renewing Let’s Encrypt SSL certificate. The certificate is issued only after the certificate authority can confirm that the selected domain names point to your hosting account.
Why this matters: Let’s Encrypt must reach your domain during validation, so an unpointed or mismatched DNS record is the most common reason issuance fails.
ns1.fastnsdns.com and ns2.fastnsdns.com. If you manage DNS elsewhere, create or update the domain’s A record so it points to the hosting IP shown in your account details.www hostname. It should resolve to the same website, usually through a www CNAME to the main domain or an A record pointing to the same hosting IP.mail.example.com, make sure that hostname also has a DNS record pointing to the mail service used by the account. Do not select mail just because it appears in the DirectAdmin list; select it when you actually use that hostname for email.dig +short example.com
dig +short www.example.com
dig +short mail.example.com Success looks like this: the main domain and every hostname you plan to include return the expected hosting destination. If one of them still returns an old IP, an empty result, or a different provider, fix DNS before requesting the certificate.
If you are moving the domain to HostKarle, DirectAdmin hosting in India explains the hosting setup and nameservers.
Why this matters: the SSL request creates the certificate and private key for the domain names you select, without requiring you to buy or upload a certificate file.
example.com. The main domain must be part of the request even when you plan to use the www version as your public address.www and mail safely.Success looks like this: DirectAdmin shows the certificate in the SSL Certificates page, with the requested hostnames listed and an active or valid status. You should then be able to open https://example.com without a certificate warning.
DirectAdmin’s ACME and Let’s Encrypt documentation explains that ACME certificates can be issued and renewed automatically. You do not need to run a server command for a normal user-level request.
www and mail correctlyWhy this matters: a certificate for only example.com does not automatically cover every hostname that visitors or mail apps may use.
On the Let’s Encrypt request page, look for the list of available domain names and subdomains. Select the names that will actually receive HTTPS connections:
| Hostname | Select it when | Check before requesting |
|---|---|---|
example.com | It is your main domain | Its DNS record points to this hosting account |
www.example.com | Visitors may open the www version | www resolves to the same website |
mail.example.com | Your mail client uses this hostname | mail resolves to the account’s mail service |
For a simple website, select example.com and www.example.com. Add mail.example.com only when your email settings use it. Including a hostname that has no DNS record can make the complete certificate request fail because Let’s Encrypt validates every selected name.
If you later change from mail.example.com to another mail hostname, request a new certificate with the new name. The certificate list in DirectAdmin is the source of truth: confirm that every hostname your users type is present there.
Success looks like this: the certificate details show the main domain plus each selected SAN (subject alternative name), and the browser shows a valid certificate for both the bare domain and www.
Why this matters: installing a certificate makes HTTPS available, but visitors can still arrive through an old http:// link until you enable the redirect.
example.com and open the domain settings. Find Force Redirect, Force SSL with https redirect, or a similarly named setting.www, non-www, or no host redirect, choose the version you want as the canonical website address.www if you want https://example.com and choose www if you want https://www.example.com. The other version should redirect to it.https:// after the certificate works. Also update hard-coded image, stylesheet, and script URLs if the browser reports mixed content.Success looks like this: opening http://example.com changes to the HTTPS URL, and opening the non-canonical host changes to your chosen canonical HTTPS address. DirectAdmin documents this setting as Force SSL with https redirect in the domain settings and SSL page.
You can also use the panel setting described above instead of adding a redirect rule manually. If you are maintaining an existing rule, our guide to redirecting HTTP to HTTPS with .htaccess covers the alternative approach. Avoid stacking several redirect rules before testing, because that can create a loop.
Why this matters: the error usually identifies a validation problem with one of the names in the request, not a problem with the certificate itself.
Work through these checks in order.
wwwRun a lookup for every name you selected:
dig +short example.com
dig +short www.example.com Both results should point to the hosting account. If the records show an old provider, remove the old A record or update the nameservers at the registrar. If you use a DNS proxy, confirm that the public DNS still points to the correct hosting destination and that the web request reaches the account.
mail separatelyIf the request fails after you selected mail.example.com, temporarily remove mail from the request and try again. If the certificate succeeds, the mail hostname is the problem. Create the correct DNS record for mail, wait for it to be visible publicly, and then request a certificate that includes it.
Do not remove a working mail DNS record just to make the website certificate pass. Instead, use the hostname that your email service actually provides and select that name in DirectAdmin.
A CAA record can restrict which certificate authorities may issue certificates for a domain. Check it with:
dig CAA example.com
dig CAA www.example.com
dig CAA mail.example.com If a CAA record exists and does not allow letsencrypt.org, update it with the DNS provider or remove it if you do not need that restriction. A CAA record on a subdomain can affect that subdomain separately from the main domain. DirectAdmin’s Let’s Encrypt troubleshooting guide also recommends checking CAA records and looking for DNS SERVFAIL responses.
If a DNS lookup returns SERVFAIL, check for invalid DNSSEC at the registrar and make sure the nameservers at the registrar match the DNS service you are editing. A mismatch means you may be changing a zone that is not publicly authoritative.
Fix the hostname that failed, then submit one new request. Repeated requests for the same unresolved domain can run into certificate authority rate limits. If the DNS is correct but the panel still reports an error, save the exact error message and ask the hosting provider to check the DirectAdmin ACME task for your account.
Why this matters: a certificate can be valid for one hostname while another hostname or redirect is still misconfigured.
Check each URL that applies to your setup:
https://example.com in a private browser window.https://www.example.com and confirm it either loads securely or redirects to your chosen canonical host.https://mail.example.com only if it is a webmail address or web endpoint. Mail apps still need the correct IMAP, POP, SMTP, and encryption settings supplied by the host.curl -I http://example.com The response should show a redirect to an HTTPS URL after Force SSL is enabled. Finally, test a few important pages and submit a form or place a test order if your website has one. Look for mixed-content warnings in the browser console if some assets still load over HTTP.
Yes, DirectAdmin can issue a free certificate through Let’s Encrypt when the hosting provider has enabled ACME for the account. HostKarle DirectAdmin plans include a free auto-renewing Let’s Encrypt SSL, so you can request it from the SSL Certificates page without buying a separate certificate.
DirectAdmin supports automatic ACME renewal. Keep the domain’s DNS records working and do not block the validation path; otherwise a future renewal can fail even if the first certificate was issued successfully.
www and mail in the certificate?Include www when visitors may use the www address. Include mail only when your email or webmail settings use mail.example.com and that hostname resolves correctly; every selected name is validated separately.
.htaccess?Yes. Open the domain settings in DirectAdmin and enable Force SSL with https redirect. This is usually the simplest option because DirectAdmin applies the redirect at the webserver level; keep only one main redirect method while testing.
The selected domain or subdomain may not point to the hosting account, may return SERVFAIL, or may have a CAA record that does not allow Let’s Encrypt. Check each selected hostname, fix DNS, wait until the change is publicly visible, and then request the certificate again.
Compare zoho mail alternatives for Indian businesses by rupee cost, IMAP access and mailbox limits,…
Compare Wix alternatives for Indian small businesses: see 3-year rupee costs, WordPress hosting, migration limits,…
Titan email price in India explained with mailbox costs, features, team totals and a comparison…
HostKarle vs Bluehost compares Indian shared hosting prices, renewal bills, email, SSL, backups, panels and…
Learn how to write blog in hindi with WordPress, Hindi typing tools, domain and hosting…
Compare Google Workspace alternatives in India by yearly rupee cost, email features and migration effort…
This website uses cookies.