Transfer errors with accounts that have add on domains
When doing live transfers on sites that have addon domains, we are getting these errors.
Site without addon domains seem to transfer fine. Its causing us greif as we need to clean up after.
-
Note: both servers were part of a cPanel dns cluster and were authoritative. The authoritative error is also somthing that occurs on around 50% if transfers - but doesn’t seem to cause issues. Overall, after transferring around 600 accounts from three servers in the past two weeks, I can say the transfer process is as bad as it’s been over the last decade and a half. More failures and problems more often.
0 -
Facing exact same issue just now, Transfer failing because subdomain doesn't exist.
Successfully transferred single domain accounts.
thanks!
/J
0 -
Temp solution: On the New server after a failed transfer, I deleted all the new dns zones except main domain of the account.
Then deleted related dns records on the main domain zone.
Added the domains manually to the CP.
Checked and all files where restored , only thing was that domain had not been "created".
On the surface seem to be working now. Not ideal for many domains.
0 -
Thanks - yeah I’ve been doing similar cleanup tasks, but it sure does suck when there can be different document roots for each domain, dns records etc - it all takes time and patience and when you have hundreds of accounts to transfer it sucks the life out of you.
1 -
Does anyone from cPanel care to post? Is this a known issue atm? Currently I'm holding off transferring some sites with many add on domains - each containing all sorts of stuff like custom DNS entries, email forwarders, different document roots etc.. I don't want these transfers to fail and leave me to clean up.
0 -
Which WHM version for the cPanel server and cPanel DNS-only servers is this happening on?
0 -
I transferred from cpanel 110.0.17 to latest (fresh installed two days ago)
I am doing single account transfers, will do another one tonight.
1 -
WoW - Not being able to move clients to a new server is going to cause major drama for me till this is fixed. The work around doesn't fill me with confidence either.. The word 'may' in a work around sounds sketchy!
0 -
Yep, Manual restore did not work either... We contacted cpanel support and this is the link they sent. Looks like there are multiple issues with transfer tool on release tier at the moment.
https://support.cpanel.net/hc/en-us/articles/19578390933143-Restoration-of-addon-tld-primary-tld-will-be-skipped-because-it-requires-that-tld-primary-tld-be-created-before-it-can-be-restored
We downgraded server to 116.0.0 but the problem still persists on that version...
https://support.cpanel.net/hc/en-us/articles/1500011373861-How-To-downgrade-cPanel-minor-version
We ended up configuring new server with stable tier (114.0.15 currently) to accommodate clients migrating to us.
https://support.cpanel.net/hc/en-us/articles/360052251053-How-to-Install-a-Specific-Version-of-cPanel-WHM0 -
I have some rather expensive severs I’m trying to decommission and the remaining clients left on them all have these add on domains - and I can’t downgrade, so looks like I’m going to need to wait.
0 -
Same!
The worst is, the document root of addon domain are using public_html for all addon!
this not happen to all user, but some user0 -
I tried it, and it didn't cause an issue. I use
Restrict document roots to public_html = Off
Allow Remote Domains = On
Allow unregistered domains = On
I'll check further.
0 -
Hey everyone! This issue was fixed as part of work on case CPANEL-42459, which was included in all versions of 116, so it would be odd to me if you're experiencing this issue when transferring your data to a version 116 server. Can you confirm that is the version of the Destination system here?
0 -
In my case, i saw an update after i did the transfer so i assume i was not on 116 (or latest).
good to know it was fixed!
1 -
My servers are 116.0.7
0 -
slim - could you create a ticket, or I can make one for you, so we can see this in action? At this time, we had expected the issue to be resolved.
0 -
What about this? https://support.cpanel.net/hc/en-us/articles/1500007983922?input_string=transfer+tool+does+not+add+addon+domains
This was created 5 days ago?
It seems it’s not fixed and cPanel knows about it?
0 -
That was actually created over a year ago, but shows it was updated 5 days ago. I believe that date coincides with the last update of our forums work, as they use the same system.
0 -
Note: I have been transfering the accounts anyway, and this morning I did the last one - It failed with this:
TRANSFER: 1 completed, 0 had warnings, and 0 failed.
RESTORE: 1 completed, 1 had warnings, and 0 failed.
RESTORE: Account “maindomain09”: Warnings
Rejecting invalid log file: logs/myaddondomain.com.au.maindomain.com.au-bytes_log
Rejecting invalid log file: logs/myaddondomain.com.au.maindomain.com.au
Rejecting invalid log file: logs/myaddondomain.com.au.maindomain.com.au-ssl_log
Failed to restore the domain “myaddondomain.com.au.maindomain.com.au”: Restoration of “myaddondomain.com.au.maindomain.com.au” will be skipped because it requires that “com.au.maindomain.com.au” be created before it can be restored.
Failed to restore the domain “myaddondomain.com.au”: Restoration of “myaddondomain.com.au” will be skipped because it requires that “myaddondomain.com.au.maindomain.com.au” be created before it can be restored.
Restoration of “myaddondomain.com.au.maindomain.com.au” will be skipped because it requires that “com.au.maindomain.com.au” be created before it can be restored.
Prerequisite domain, “com.au.maindomain.com.au” is not referenced in the restore file and does not preexist.
Restoration of “myaddondomain.com.au” will be skipped because it requires that “myaddondomain.com.au.maindomain.com.au” be created before it can be restored.
Prerequisite domain, “myaddondomain.com.au.maindomain.com.au” is not referenced in the restore file and does not preexist.
This system is not authoritative for the zone “xxxxxxxx.com.au”.
Contact “xxxxxxxx.com.au”’s registrar and set that domain’s nameservers to “ns1.myhostingcompany.com” and “ns2.myhostingcompany.com”. (For registrar information, visit https://client.rdap.org/?object=xxxxxxxx.com.au&type=domain.)
You must also make “ns1.myhostingcompany.com” and “ns2.myhostingcompany.com” resolve to this server.
This system is not authoritative for the zone “maindomain.com.au”.
Contact “maindomain.com.au”’s registrar and set that domain’s nameservers to “ns1.myhostingcompany.com” and “ns2.myhostingcompany.com”. (For registrar information, visit https://client.rdap.org/?object=maindomain.com.au&type=domain.)
You must also make “ns1.myhostingcompany.com” and “ns2.myhostingcompany.com” resolve to this server.Both the source and destination servers were CloudLinux8.8 with 116.0.7 of cPanel installed.
In the above instance, I simply cleaned up the DNS after transfer and readded the domain into the DOMAINS section of cPanel. There was no custom zone for the add on domain, so it was easy for us, but many haven't been.
The old server will now be decommissioned - this really needs to be addressed thou as it makes transfers very painful.0 -
Well it seems the situation has changed since we all went to bed last night!
The original case I linked, CPANEL-42459, was indeed fixed, but apparently it introduced an additional problem that needs to get solved with the one you just linked, slim, CPANEL-43609. That is now scheduled to be fixed in version 118.
I've requested this gets fixed in version 116 as well as this is an important case, and I'll be sure to post updates here as I get them!
0 -
Update - this will be included in the next 116 build as well!
0 -
When will next build come out? This is quite a critical issue
0 -
I'm hoping the answer is "this week" but I don't have an official ETA at this point.
0 -
I have a similar error, looking forward to receiving the latest update. cpanel in use: 116.0.7
0 -
Hi! I can see now that 116.0.9 has been released with a "Fixed case CPANEL-43609: Revert "Domain restoration failure when a primary domain is parked under a subdomain"."
Does this mean that the original case/fix (I dont remember what it was about) has now been rolled back and thus is unsolved or that both cases/fixes are now fixed?
0 -
This just means that we reverted the work that caused the original problem, but the ultimate fix is still not in place yet.
0 -
I am a hosting provider, can the last update be sooner?
Thank you!
0 -
116.0.9 is now up to the Release tier, so that should help with a majority of people seeing these issues.
0
Please sign in to leave a comment.
Comments
32 comments