Perhaps this point has been brought up some where and I missed it. I did a search found some older threads, I think 2017 being the latest one I've seen. And it seems to indicate that this is not possible.
So apparently you can't add a secure certificate to a "subdomain" in DirectAdmin? Is that correct?
(For context, "subdomain" here is referring to the Dashboard -> Sub-Domains Setup area)
The work-around I saw in the forum search was to create the subdomain as a "domain" in the user's panel, then you can add a certificate to this "domain".
(i.e. Dashboard -> Domain management -> Add New)
If this is the solution, I don't really have a problem with it. I just wanted to make sure that information was correct.
I do wonder though... everyone that migrated their servers from cPanel to DirectAdmin, did any of your subdomains on cPanel have certificates and now are they working on DirectAdmin?
The line between addon domains, subdomains, and parked domains has really been blurred. I really wouldn't mind an industry wide shift into recognizing all of these titles as just "addon" domains or "additional" domains, whatever you want to call them.
A parked domain (alias) is just a domain name that shares the same DocumentRoot as it's parent domain name.
A subdomain is just a domain name that leeches part of it's name from it's parent domain name, and probably has it's own DocumentRoot.
An addon (additional) domain is just a different domain name that uses it's own DocumentRoot.
All three operate within the same user space as the parent domain (i.e. the same Linux username space... what I refer to as the account).
All three of these can be clumped into one entity that takes two parameters... the domain name (or the subdomain, if you want to use a name that leeches off of it's parent) and the DocumentRoot (as it exists on the file system) to point to.
So apparently you can't add a secure certificate to a "subdomain" in DirectAdmin? Is that correct?
(For context, "subdomain" here is referring to the Dashboard -> Sub-Domains Setup area)
The work-around I saw in the forum search was to create the subdomain as a "domain" in the user's panel, then you can add a certificate to this "domain".
(i.e. Dashboard -> Domain management -> Add New)
If this is the solution, I don't really have a problem with it. I just wanted to make sure that information was correct.
I do wonder though... everyone that migrated their servers from cPanel to DirectAdmin, did any of your subdomains on cPanel have certificates and now are they working on DirectAdmin?
The line between addon domains, subdomains, and parked domains has really been blurred. I really wouldn't mind an industry wide shift into recognizing all of these titles as just "addon" domains or "additional" domains, whatever you want to call them.
A parked domain (alias) is just a domain name that shares the same DocumentRoot as it's parent domain name.
A subdomain is just a domain name that leeches part of it's name from it's parent domain name, and probably has it's own DocumentRoot.
An addon (additional) domain is just a different domain name that uses it's own DocumentRoot.
All three operate within the same user space as the parent domain (i.e. the same Linux username space... what I refer to as the account).
All three of these can be clumped into one entity that takes two parameters... the domain name (or the subdomain, if you want to use a name that leeches off of it's parent) and the DocumentRoot (as it exists on the file system) to point to.