"Convert addon domain" tool not seeing most addon domains
I have a LW licensed server and my support over there directed me to a link that explains how to create an addon domain vs a subdomain in the new combined domain tools. The process for creating and addon domain is exactly what is followed when creating addon domains, yet this domain and many other addon domains do not show up as options in our "convert addon domain to main domain" tool.
I'm not sure if these were old "addon domains" that were added before the switch over to the combined domain tool was implemented, so I'm not sure if this bug is related to how he old addon domains were switched over or if there is a bug with the current "Create domain" tool in cpanel.
Either way I need to report somewhere that there is a bug in one or both of those places where alternate (non-subdomain) domains for accounts on my server are not showing up in that convert tool.
My LW rep told me that the "addon domain" I was trying to convert is a "subdomain" and not an "addon domain" which is why it wasn't showing up. The problem with this is that the domain in question is clearly not a subdomain, nor would it have been configured that way as it was a completely-different.com from the main-domain.com (and literally only had 1 dot character, which was part of the ending ".com" in the domain, so there is no way this could even be accidentally construed as a "subdomain".
Just throwing it out there you guys might want to double check why something like this might happen as I'm sure I'm not the only one that has or will run into this.
-
Hey there! Do you have any specific replication steps for this process? I haven't heard any similar reports and a quick look at the tool on a test machine shows me all the addon domains I am expecting. When the tool was originally released it was able to convert existing addon domains, so the age will not matter.
0 -
I am having a similar problem, doing some housekeeping in preparation to move to a new server. The addon domains in question belong to an account whose primary domain not longer exists.
0 -
I would still need replication steps in order to perform additional troubleshooting on this issue, as I'm not able to reproduce the problem on a test machine. If you can get me those I'd be happy to take a look!
0 -
The problem is that the domains were parked and not addon. It is not obvious from the domain manager what they are. My issue has been resolved.
1 -
I'm hoping the feature request at https://features.cpanel.net/c/100-remove-subdomain-requirement-for-addon-domain-creation will help clean up the cPanel >> Domains interface a bit so we can remove some of that confusion in the future.
0 -
Added a comment to the feature request, thanks for pointing it out.
Now just need to fix the ‘unnamed user’, hard to follow the conversation.
0 -
Thanks for that - I review those every other week so we'll see the comment!
You can change the name inside your cPanel support account - if you're not seeing that as an option please email cs@cpanel.net so they can adjust your account.
0 -
It says it is set automatically. I see a great many posts with unnamed user. Earlier post showed my name. Will contact support.
1 -
I just wanted to follow up to say our team is looking into this now - if I hear more on my end first I'll let you know!
0 -
They were able to get that fixed so you're all set!
0 -
only partially, updated my ticket
1 -
cPRex I cannot give you steps to "replicate" the issue as I'm pretty sure these were old "addon domains" that are erroneously classified as "subdomains" when they should just be a "domain", when the switch to the "combined" domain tool occurred (guessing).
I can provide you access to my server where you can poke around to see what is going on which might be helpful since I cannot give you steps to reproduce it.
Here is a screenshot I took that shows just one account that has none of its 2 addon domains listed, left window shows the convert addon domains list (sorted by account name) and the right window shows an account with 2 addon domains that are not listed:
0 -
Sure - if you'd like to make a ticket so we can access the system we'd be happy to check it out!
0 -
cPRex Sure, could you give me a link where I could do that? I cant seem to find it and I also believe the last time I tried to do that it wouldn't let me because my LiquidWeb support contract, so I would need a ticket submission that would not have that limitation....
0 -
If your license is purchased from us you would be able to make that ticket directly from WHM. If the license was purchased elsewhere you would need to contact that provider for support and then they would escalate the issue to us if necessary.
0 -
Honestly, that is so ridiculous. I understand the why but I honestly don't agree with it. You guys are the developer of the software, there should be a way I can open a ticket directly with you regarding a possible bug in your software. I don't see why LiquidWeb needs to be involved since they literally do nothing but slow down the communication process by being in the way.
But sure. I'll open a ticket with them.
0 -
Could you email cs@cpanel.net with all the information you have and then I can review that?
0
Please sign in to leave a comment.
Comments
17 comments