Our features site is undergoing a refresh! Be sure to explore the revamped site and discover our latest product roadmap launching here on Monday, March 18th.

Domains checkbox ""Share document root..."

VF shared this idea 21 months ago
Not Planned

Within the Domains section of cPanel the checkbox that says "Share document root (/home/username/public_html) with 'domain.tld'" is mislabeled. If you need an addon domain that shares the same document root... then this doesn't make sense. When this box is checked, an alias domain is created instead of an addon domain.

If you have a 3rd party SSL on your main domain, alias domains will not be replaced by AutoSSL. Unchecking the box creates an addon domain instead, which can be checked by AutoSSL despite having a 3rd party SSL on the main domain. In our case, both the main domain and the desired addon domain were to share a document root. We could not figure out why the new domain was being excluded from autoSSL and lost quite a bit of time figuring it all out.

Replies (1)

photo
1

By definition, an addon domain is a separate document root with a separate domain.

AutoSSL will not replace any certificates installed from a third party unless you have the "Allow AutoSSL to replace invalid or expiring non-AutoSSL certificates." option selected in WHM >> Manage AutoSSL.

At this point, I'm going to mark this as "not planned" since it seems you're experiencing the intended behavior. If you think things are not working how they should be, please contact our support team directly so we can investigate the issue on your machine.

photo
1

I believe you misunderstood.. I do not want it to replace an existing one. I wanted it to issue one for the new domain I was adding. But when I add the domain and check that box I will not get an SSL for it

photo
1

The problem is that the description next to that checkbox is not appropriate. It simply needs to say alias domain... not all of that stuff about a path

photo
1

Hello?

photo
1

You should contact our support team through a ticket so we can investigate this issue.

photo
1

No thank you, I don't have the time. I was trying to help you guys out. If you check that box AutoSSL will not work on the domain you are adding. If you want the same document root and you want AutoSSL to work on the domain you are adding, you have to uncheck the box then specify the same root. I was simply saying the verbiage should be updated so that people don't lose a bunch of time trying to figure out what is going on.

photo
1

I still believe this is working as intended. AutoSSL should issue a certificate for any type of domain on the account, whether or not they share a document root. It does sound like there is an issue with your configuration, but we would need a ticket created with our support team to investigate.

photo
1

Some further background here. We have a multisite setup. The primary domain is covered under a Digicert SSL as they wanted liability coverage should the SSL on their main site be compromised. New domains share the same public_html folder, and simply redirect to primarydomain.com/newdomainsubsite.


In the past we would specify addon domain when adding a new domain. Now we are left scratching our head as the add domain screen simply says "share document root..." So we leave that box checked and add the domain. There is nothing on that page that indicates this is not the correct behavior or that a domain will be added as an alias. Then when auto SSL attempts to fetch an SSL, it cannot apply it because it is trying to apply a SAN certificate and the primary domain has a Digicert SSL. This results in the new domains being added, sharing the same public_html folder as desired, but without the ability to be secure. Is it just me or does this seem to be the opposite of what cPanel was likely going for? I assume you all were aiming for securing as many domains as possible, as easily as possible.

photo
1

I believe that if the primary domain is secured by a 3rd party certificate, the new domain should automatically be added as an addon domain so that AutoSSL can automatically secure it. Otherwise you end up with a bunch of domains added that cannot have an SSL installed without replacing the 3rd party certificate.

photo
Leave a Comment
 
Attach a file