Adding a domain not behaving as expected
-
Hey there! If you created an addon domain, it's normal that you get an awkward-looking subdomain as part of the account creation process. This won't really be used for anything except some internal Apache functions. It's more clear using an example with fewer subdomains - if I have domain.com and create an addon domain of otherdomain.com, you should expect to see otherdomain.domain.com in the Apache configuration somewhere. So, I think what you're seeing is at least partly expected, but it doesn't mean something else couldn't be wrong. What problem do you get when trying to force the https redirection? 0 -
Ok, thanks for your response. In the Domains section of cPanel having added the domain, I see two new entries: angelalear.domain.io "Force HTTPS Redirect" is unavailable, with the message, "Addon and parked domains inherit their HTTPS redirect status from their associated subdomain." What subdomain is it referring to? This is itself in fact a subdomain! angelalear.domain.io.blog.domain.io Here, the "Force HTTP Redirect" is fixed at "Off" with the tooltip, "You cannot activate HTTPS Redirect because AutoSSL is not currently active for this domain or the SSL certificate is not valid." I mean that message is clear, but I don't see a way to create an SSL certificate for such a domain! What am I missing? 0 -
Please make sure to anonymize any domains when posting to the Forum, for security reasons. On the right of the page you should see a gear wheel - if you click that, you'll get the option to see all the subdomains on the page as well. Can you see if that helps get things working? 0 -
Please make sure to anonymize any domains when posting to the Forum, for security reasons.
Oh, I will, but I was hoping people might visit anyway I will check out your suggestion, thanks.0 -
Please make sure to anonymize any domains when posting to the Forum, for security reasons. On the right of the page you should see a gear wheel - if you click that, you'll get the option to see all the subdomains on the page as well. Can you see if that helps get things working? 84377
Well I tried that, but in fact the option was to hide them, rather than show them. They were all already visible.0 -
Do you have root access to the server? If so, we might need to take a look at this one. If not, you'd need to speak with your host to have them check the domain situation. 0 -
Do you have root access to the server? If so, we might need to take a look at this one. If not, you'd need to speak with your host to have them check the domain situation.
I do, it"s my own VM.0 -
Could you submit a ticket to our team so we can check it out? Post the number here so I can follow along! 0 -
Hmm"I"ll work out how to do that! Thanks. 0 -
Ok, well, after being redirected to at least half a dozen different pages, I really am not sure what the status is of this ticket! I believe I need to enable access via SSH but I don"t know which ports are needed"I did see a list of IPs" 0 -
Thanks for that - I'm following along now! 0 -
I see our team was able to check the DNS settings and confirmed they did not properly resolve to the server. Once those are configured, the https redirection will work as expected. 0 -
We too have this issue. We have a cpanel account for lets call it domain.com. There is a website associated with the main domain and that is secured with an SSL. The Force HTTPS Redirect option is available and on for that domain. We then wanted to add another site to this cpanel account as an addon domain, lets call it domain.testdomain.com. We added domain.testdomain.com as another domain without sharing the same document root. the root for the new domain is a folder called domain.testdomain.com, within public_html. As you said, cpanel created a junk subdomain for this new addon domain that serves no purpose. We do not have this junk subdomain setup within DNS as we don't want any additional traffic driven to the account through that junk subdomain. Let's encrypt was able to issue an SSL for domain.testdomain.com, but we are unable to turn on the option Force HTTPS Redirect. It says "Addon and Parked domain inherit HTTPS redirect status from their associated subdomains." That can't be true can it? Why would anyone want the junk subdomain resolvable? Why would the setting to force HTTPS be dependent on the subdomain status, when the SSLs can be separate?
0 -
@vf-hostmaster - that is indeed correct. I don't have an immediate answer to make this situation better for you, but I can say that we're working on a long-term project to remove those "junk" domains and links between domains. It really shouldn't matter if it's a park/addon/sub/whatever type of domain, but that is how cPanel has been structured since day 1 so it's taking some effort to get that removed and reorganized.
0 -
Thank you. I believe that is the best response you could have given without having an immediate solution.
0 -
You're very welcome!
0
Please sign in to leave a comment.
Comments
17 comments