Removing associated subdomains
-
Hey there! That subdomain is actually still a requirement, as that is how we create the Apache vhost. You can see this information in the cPanel >> Domains screen: so you won't want to go too crazy on cleaning or removing those. 0 -
Thanks, but maybe I am mixing something up. I had recently added new domains to a client with the updated Domains screen and none of those newly added domains had an associated subdomain. However a domain that was added prior to the Domains screen update and the removal of the addon domains screen, still has an associated subdomain. If it is a requirement, why do the newly added domains not have any? Thanks! 0 -
Can you click the gear wheel in the top right of your screenshot and see if that gives you the option to show associated subdomains? They may just be hidden from your interface to avoid confusion. 0 -
I know about the gear and option, I did already click it prior to the screen shot so that I could see the associated sub domain for the first domain listed. But regardless here is the image showing the present status of the gear button. To expand on it I can show the pages when you manage the domains, first being the old domain and the second the newer: 0 -
Thanks for that confirmation. I'm honestly not sure, so it might be best to submit a ticket to our team so we can check the system directly. 0 -
Ticket ID #94536008 0 -
Thanks for that - I'm following along with that ticket on my end now. 0 -
So an update for everyone, it appears I was getting confused with the new Domains interface and being unable to clearly differentiate add-on and parked/alias domains. To clarify there is no clear distinction in the new Domains interface which should probably be fixed, but here are the general rules I have now gathered: - Parked/Alias domains can only be for the primary domain
- If the check-box "Share Document Root" is unchecked, even with the same path as the primary domain, it will become an add-on domain with an associated subdomain
- You can confirm if a mistake like this was made by going here:
cat /var/cpanel/userdata/[user]/main
- You can confirm if a mistake like this was made by going here:
- Add-on domains require an associated subdomain with cPanel for vhost reasons, don't understand that fully
- Only way to prevent associated subdomains from resolving is modifying your DNS entries
- Add-on domains shouldn't create additional service subdomains, but you can remove them by following this:
0 -
Thanks for sharing all that! 0 -
What's the process for removing the auto-SSL for associated subdomains that are not needed? DarkxPunk your image is not showing.
0 -
You shouldn't need to do anything special with the AutoSSL for the domain. Once the subdomain is removed it will remove the Apache vhost and SSL data.
0 -
cPRexI've removed a subdomain from the DNS, but it still receives auto-SSL requests.
0 -
Can you clarify what "removed a subdomain from the DNS" means? I would need to know what specific actions were taken in the interface that got us to this point so I can let you know what to do next.
0 -
Same situation, added an "add-on domain" in the old cPanel version with the associated domain. I removed the associated domain from the DNS manager, but there is still a request for the auto-SSL.
0 -
So you used the Zone Editor to specifically remove that DNS record for the subdomain?
If that's the case, I would expect the AutoSSL requests to continue as the domain still exists on the server. Do you see the domain in cPanel >> Domains on the account?
0 -
The associated subdomain does not exist, but the add-on domain does.
0 -
There you go - once you remove that addon domain I would expect the AutoSSL requests to stop. The additional addon domain is what allows the domain to function in Apache, so getting rid of that should fix everything.
0 -
I need the add-on domain
0 -
I guess I don't understand your situation - how would the original subdomain be linked to an addon domain?
Currently there are four types of domains in cPanel, although we're hoping to change this in the near future to make things easier to manage:
-The main domain of the account
-Parked domains - just a link created in Apache that points domainA to the content of domainB
-Subdomains - this one should be self-explanatory
-Addon domains - this is the confusing one. An addon domain is both a separate domain, such as addondomain.com, but also requires a subdomain in the format of addondomain.maindomain.com in order to function properly in Apache in the cPanel environment.If you deleted the subdomain you'll likely run into issues in the future with the addon domain.
If you don't have root access to the server you'll likely need to speak with your host so they can confirm what does and does not exist in the Apache configuration.
0 -
The main domain is no longer pointed to the server. The add-on domain is. The associated subdomain is for the main domain. I honestly don't care what domain or subdomain exists on the server. I just want AutoSSL to stop sending me 20 messages a day saying the subdomain SSL can't be created.
I have root access.
0 -
Oh! The main domain not existing is a different situation.
There isn't really a way to "fix" the core issue of the domain not existing but you can workaround it by going to cPanel >> SSL/TLS Status and click the "Exclude from AutoSSL" button there to stop AutoSSL from trying to issue the certificate.
0 -
That seems to have fixed it!
0 -
I'm glad that's all it took!
0
Please sign in to leave a comment.
Comments
23 comments