Tool that allows me to easily convert local addon domains into their own cPanel accounts
As a Reseller, I want a tool that allows me to easily convert local addon domains into their own cPanel accounts, so that I can easily split accounts with existing addon domains into multiple cPanel accounts.
I have had a few people ask about taking an addon domain and *easily* making it a main account. It would be great if we had something like a transfer tool for addon domains. Basically create the new account and transfer all the files over. Right now they have to delete the addon domain add the new account then ftp (or scp rsync etc) their files to the new account.
This is a feature that has been migrated over from the cPanel Forums. All previous comments and discussions concerning this feature can be located at:
http://forums.cpanel.net/f145/tool-migrate-addon-its-own-full-account-please-157953.html
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
https://documentation.cpanel.net/display/ALD/Convert+Addon+Domain+to+Account
This feature is included in cPanel & WHM version 56 as a first iteration. That means that we are not completely done with development for the feature. We will continue working on this for 58 to more round out our feature. I have included a list of things we are converting and things that we have not yet gotten to. Thanks eveyone for your support.
Data migrated
The Convert Addon Domain to Account feature allows users to migrate the following data:
Data not migrated
The Convert Addon Domain to Account feature does not allow users to migrate the following data:
This is available in cPanel & WHM version 56. Comments are now locked, but if you require any assistance you can open a ticket with our support team, email benny (benny@cpanel.net) or ask on twitter (@cpaneldev).
https://documentation.cpanel.net/display/ALD/Convert+Addon+Domain+to+Account
This feature is included in cPanel & WHM version 56 as a first iteration. That means that we are not completely done with development for the feature. We will continue working on this for 58 to more round out our feature. I have included a list of things we are converting and things that we have not yet gotten to. Thanks eveyone for your support.
Data migrated
The Convert Addon Domain to Account feature allows users to migrate the following data:
Data not migrated
The Convert Addon Domain to Account feature does not allow users to migrate the following data:
This is available in cPanel & WHM version 56. Comments are now locked, but if you require any assistance you can open a ticket with our support team, email benny (benny@cpanel.net) or ask on twitter (@cpaneldev).
How would you want to handle the files.
1) Transfer all the files from the document root of the addon domain?
2) Transfer some of the databases?
3) Transfer all the forwarders and email settings?
How would you want to handle the files.
1) Transfer all the files from the document root of the addon domain?
2) Transfer some of the databases?
3) Transfer all the forwarders and email settings?
The files, forwarders, and email settings could be done relatively easy. Databases, though ... not so much. Databases would likely need some manual intervention to determine which ones should be moved.
The files, forwarders, and email settings could be done relatively easy. Databases, though ... not so much. Databases would likely need some manual intervention to determine which ones should be moved.
The ability to automatically transfer email accounts & email forwarders, with their settings of that addon domain would be important too.
The ability to automatically transfer email accounts & email forwarders, with their settings of that addon domain would be important too.
The domain and relate subdomains, files in the document root, email accounts, email forwarders, etc... Anything specific to the domain would be ideal. It would be possible to include databases as well if a list of databases was provided.
Something like, "Please choose which databases are associated with this add-on domain: (list of databases)." The issue you are going to face no matter what is that script configuration files will need to be updated manually but this is an issue we all face now even without such a tool to help us out at all.
Copying the databases and any users for those databases, re-naming them for the new account, and then applying the old permissions and passwords would be ideal as well, but unsure how feasible it would be in an automated fashion.
The domain and relate subdomains, files in the document root, email accounts, email forwarders, etc... Anything specific to the domain would be ideal. It would be possible to include databases as well if a list of databases was provided.
Something like, "Please choose which databases are associated with this add-on domain: (list of databases)." The issue you are going to face no matter what is that script configuration files will need to be updated manually but this is an issue we all face now even without such a tool to help us out at all.
Copying the databases and any users for those databases, re-naming them for the new account, and then applying the old permissions and passwords would be ideal as well, but unsure how feasible it would be in an automated fashion.
that is not big job to do it manualy ... :s
that is not big job to do it manualy ... :s
It's also not a big job to create virtual hosts manually, to install Apache manually, or to do a myriad of things that cPanel handles for us. If you want to do it manually - you can - the tool certainly isn't going to prevent you from doing it manually.
It's also not a big job to create virtual hosts manually, to install Apache manually, or to do a myriad of things that cPanel handles for us. If you want to do it manually - you can - the tool certainly isn't going to prevent you from doing it manually.
I would also like to see the ability do the reverse too.
I would also like to see the ability do the reverse too.
It would be good to converted parked domains (including mail) into a separate account as well.
It would be good to converted parked domains (including mail) into a separate account as well.
Domains, emails, subdomains and files makes sense. Databases no.
Domains, emails, subdomains and files makes sense. Databases no.
Cool, I would like also the opposite convert a cPanel account into a simple addon domain.
Cool, I would like also the opposite convert a cPanel account into a simple addon domain.
Yes it looks not that complicated and will make webmasters and other apps very easy to make the job in both ways, split or merge.
Split:
1. Select added domains to split.
2. Select elements to split (files, ssl,db, etc) would be like selecting the elements in an account transfer.
3. Script runs new user process like any other new account
4. New account created.
6. Moves files, changes permissions
7. Changes database name to new user prefix warns about this. Changes apache configs as on any account delete and account create.
8. Done, account splitted.
Anyway I manually do this...
Merge will be very similar, not complicated to put on a script/ feature I think, hope this feature sees a green light soon.
Yes it looks not that complicated and will make webmasters and other apps very easy to make the job in both ways, split or merge.
Split:
1. Select added domains to split.
2. Select elements to split (files, ssl,db, etc) would be like selecting the elements in an account transfer.
3. Script runs new user process like any other new account
4. New account created.
6. Moves files, changes permissions
7. Changes database name to new user prefix warns about this. Changes apache configs as on any account delete and account create.
8. Done, account splitted.
Anyway I manually do this...
Merge will be very similar, not complicated to put on a script/ feature I think, hope this feature sees a green light soon.
A couple other options that would be good to have along with what luigidelgado posted
1. Option to take a backup of the original account before anything is done.
2. This is probably a given, but remove the addon domain.
A couple other options that would be good to have along with what luigidelgado posted
1. Option to take a backup of the original account before anything is done.
2. This is probably a given, but remove the addon domain.
For "almost atomic" operation, create a temporary new domain name and move the addon domain content to the temporary domain. Once completed, remove the addon domain and rename the temporary domain to the new full domain.
For "almost atomic" operation, create a temporary new domain name and move the addon domain content to the temporary domain. Once completed, remove the addon domain and rename the temporary domain to the new full domain.
As long as a feature is added to this so that you could select specific MySQL databases to be transferred, this would be amazing! Features should include:-
- Transfer addon domain to (newly created by script) cPanel account
- Transfer all files from addon domain document root
- Select specific MySQL databases from former cPanel account to transfer
- Transfer any subdomains from this addon domain
- Possibly more I've missed out!
This would be very helpful for me and many others!
As long as a feature is added to this so that you could select specific MySQL databases to be transferred, this would be amazing! Features should include:-
- Transfer addon domain to (newly created by script) cPanel account
- Transfer all files from addon domain document root
- Select specific MySQL databases from former cPanel account to transfer
- Transfer any subdomains from this addon domain
- Possibly more I've missed out!
This would be very helpful for me and many others!
IMHO useless feature, which profit for the business?
IMHO useless feature, which profit for the business?
Not necessary.
Not necessary.
This feature would be very nice for moving addon domains that have lots of email traffic to minimize as much down time as possible. Depend on how your accounts and settings are configured, you would loose valuable emails that some companies would like to avoid loosing.
There are also those that use there domain to host customer emails and see thousands of emails an hour. Being able to minimize domain downtime and seamlessly move email acount would be a huge benefit to lots of web administrators.
This feature would be very nice for moving addon domains that have lots of email traffic to minimize as much down time as possible. Depend on how your accounts and settings are configured, you would loose valuable emails that some companies would like to avoid loosing.
There are also those that use there domain to host customer emails and see thousands of emails an hour. Being able to minimize domain downtime and seamlessly move email acount would be a huge benefit to lots of web administrators.
cPanel is a control panel for years, I cant understand that why didnt they implemented such an important feature before.
account => addon and addon =>account both very importand features.
Behind the manual operations, there is no way for moving email account data from/to addon domain.
And the work (move files, db, email forwarders etc) is not a small work to do manually for a reseller. FTP costs hours for reseller.
cPanel is a control panel for years, I cant understand that why didnt they implemented such an important feature before.
account => addon and addon =>account both very importand features.
Behind the manual operations, there is no way for moving email account data from/to addon domain.
And the work (move files, db, email forwarders etc) is not a small work to do manually for a reseller. FTP costs hours for reseller.
I came here after searching the forum, where this feature has been requested since 2010. (http://forums.cpanel.net/f145/tool-migrate-addon-its-own-full-account-please-case-8970-a-157953-p5.html)
This feature should have been implemented years ago, and IMHO is one of the most important features that cPanel is lacking.
It is a very lengthy process to manually backup and restore all files of an addon domain into a new cpanel account (website data, database, email accounts, forwarders, cron jobs). It requires changing ownership of files as well, and can become a real pain, if you get it wrong.
I have had this requested by customers a few times now, and they expect service, so we have to sit down and do it, or end up with a disgruntled customer... so pardon me when I say, I am a slightly disgruntled cpanel customer, especially knowing that you have this feature in "planning phase" for years now.
Make this happen, there is a reason it is so high up in the list.
I came here after searching the forum, where this feature has been requested since 2010. (http://forums.cpanel.net/f145/tool-migrate-addon-its-own-full-account-please-case-8970-a-157953-p5.html)
This feature should have been implemented years ago, and IMHO is one of the most important features that cPanel is lacking.
It is a very lengthy process to manually backup and restore all files of an addon domain into a new cpanel account (website data, database, email accounts, forwarders, cron jobs). It requires changing ownership of files as well, and can become a real pain, if you get it wrong.
I have had this requested by customers a few times now, and they expect service, so we have to sit down and do it, or end up with a disgruntled customer... so pardon me when I say, I am a slightly disgruntled cpanel customer, especially knowing that you have this feature in "planning phase" for years now.
Make this happen, there is a reason it is so high up in the list.
Guys, correct me if I'm wrong but isnt this just a case of:
/var/cpanel/users/* | grep -vE "DNS=|XDNS" | cut -d= -f2 | awk {'print
"/scripts/wwwacct "$1" "substr($1,0,7)" t3mp4321"'}
Guys, correct me if I'm wrong but isnt this just a case of:
/var/cpanel/users/* | grep -vE "DNS=|XDNS" | cut -d= -f2 | awk {'print
"/scripts/wwwacct "$1" "substr($1,0,7)" t3mp4321"'}
I want to see the ability do the reverse too.
I want to see the ability do the reverse too.
Just wanted to bump this one. This would be a very useful feature. Simply a "convert from add-on to full cpanel" , it grabs the document root for said add-on domain, all emails, and simply provides a checkbox list of mysql databases to move.
Granted of course these databases would need to be dumped and re-imported into new database names to match the appropriate cPanel user I think this is the most straight forward way to accomplish such.
Just wanted to bump this one. This would be a very useful feature. Simply a "convert from add-on to full cpanel" , it grabs the document root for said add-on domain, all emails, and simply provides a checkbox list of mysql databases to move.
Granted of course these databases would need to be dumped and re-imported into new database names to match the appropriate cPanel user I think this is the most straight forward way to accomplish such.
I get requests for this from clients all the time, this would be a very useful feature.
I get requests for this from clients all the time, this would be a very useful feature.
Hello,
A lot of clients have asked us for this tool in the last 2 years.
Would be great to see it implemented.
Hello,
A lot of clients have asked us for this tool in the last 2 years.
Would be great to see it implemented.
The request under discussion here is the ability to promote an Addon Domain, and related assets, into its own cPanel account. Requests, votes and discussions for the reverse (consolidating accounts) need directed at the following request: http://features.cpanel.net/responses/as-a-reseller-i-want-the-ability-to-easily-merge-multiple-cpanel-accounts-and-their-addonparked-domains-into-a-single-cpanel-account-so-that-i-can-easily-c
The request under discussion here is the ability to promote an Addon Domain, and related assets, into its own cPanel account. Requests, votes and discussions for the reverse (consolidating accounts) need directed at the following request: http://features.cpanel.net/responses/as-a-reseller-i-want-the-ability-to-easily-merge-multiple-cpanel-accounts-and-their-addonparked-domains-into-a-single-cpanel-account-so-that-i-can-easily-c
Hello,
Everything that is obviously owned by the addon domain should be migrated, that's e-mail accounts and forwarders.
Anything that is accessible from the addon domain account web path folder should be copied and not moved, the user can delete unwanted files but not restore files if they were shared by multiple addmin domains.
Anything that is not sure should be proposed : databases should be shown as a list with checkboxes or something similar, databases should be renamed to have the new user's prefix for database and usrname and password should be kept if possible.
A warning about database connect files needing to be updated should be given.
This type of change is a pain to do on a daily basis, not highly complicated but is alot of waisted time over the years.
Hello,
Everything that is obviously owned by the addon domain should be migrated, that's e-mail accounts and forwarders.
Anything that is accessible from the addon domain account web path folder should be copied and not moved, the user can delete unwanted files but not restore files if they were shared by multiple addmin domains.
Anything that is not sure should be proposed : databases should be shown as a list with checkboxes or something similar, databases should be renamed to have the new user's prefix for database and usrname and password should be kept if possible.
A warning about database connect files needing to be updated should be given.
This type of change is a pain to do on a daily basis, not highly complicated but is alot of waisted time over the years.
The ability to automatically transfer email accounts & email
forwarders, with their settings of that addon domain would be important
too.
The ability to automatically transfer email accounts & email
forwarders, with their settings of that addon domain would be important
too.
mocha host is a big hosting i also use their all feature. In their setting have option that you want to use for a handle ad don.
mocha host is a big hosting i also use their all feature. In their setting have option that you want to use for a handle ad don.
There is a new feature of a WHM plugin called "Restore Manager" that makes it possible to easily convert an addon domain to become its own cpanel account. Here's a video of how it works:
http://www.youtube.com/embed/c096y6ntRgo
Here's their website:
http://rem.gk-root.com/Overview
(Scroll down a bit and you'll see this feature is called "Extract addon domain to new account".)
We own several licenses of this plugin for the last year, and this is a new feature they just added a week ago. (We've been using this plugin to allow our customers to manage their own restores of files from cpanel backups.)
BTW - I think cpanel should purchase this entire plugin and make it core. Everything it does is something WHM/cpanel should already be doing...
There is a new feature of a WHM plugin called "Restore Manager" that makes it possible to easily convert an addon domain to become its own cpanel account. Here's a video of how it works:
http://www.youtube.com/embed/c096y6ntRgo
Here's their website:
http://rem.gk-root.com/Overview
(Scroll down a bit and you'll see this feature is called "Extract addon domain to new account".)
We own several licenses of this plugin for the last year, and this is a new feature they just added a week ago. (We've been using this plugin to allow our customers to manage their own restores of files from cpanel backups.)
BTW - I think cpanel should purchase this entire plugin and make it core. Everything it does is something WHM/cpanel should already be doing...
I just got a notification that status is now "Planned"! Any ETA?
I just got a notification that status is now "Planned"! Any ETA?
Great news, a cPanel implementation of their own shall be better than what third parties could do....
Great news, a cPanel implementation of their own shall be better than what third parties could do....
Nice, this is something that would help users allot. I had this need several times, when customers becomes resellers and wants to move addons to accounts or when they want to separate accounts from addons to its own account. This is actually something that popups in support tickets allot, how to migrate the addon to a real account. And its painful for the user as well, because you cannot actually add the real account until the addon is removed, which means he suffers downtime when having to remove the addon and then transfer the files and config.
A way to automate this from WHM would solve this problem from everyone. Good to hear this feature will come eventually.
Nice, this is something that would help users allot. I had this need several times, when customers becomes resellers and wants to move addons to accounts or when they want to separate accounts from addons to its own account. This is actually something that popups in support tickets allot, how to migrate the addon to a real account. And its painful for the user as well, because you cannot actually add the real account until the addon is removed, which means he suffers downtime when having to remove the addon and then transfer the files and config.
A way to automate this from WHM would solve this problem from everyone. Good to hear this feature will come eventually.
Yes, it would be very nice.
Yes, it would be very nice.
We need it.
We need it.
Please cPanel, do it and save us our time!
Please cPanel, do it and save us our time!
Can't believe we're still waiting for this.
Can't believe we're still waiting for this.
Yes, what are you waiting for...
Yes, what are you waiting for...
5 years in the making...!
Good lord!
5 years in the making...!
Good lord!
This would save us from a lot of headaches.
+1
This would save us from a lot of headaches.
+1
Hello,
A lot of people have asked us for this tool in the last 2 years.
Would be great to see it implemented.
Hello,
A lot of people have asked us for this tool in the last 2 years.
Would be great to see it implemented.
Any update on the timeline Kenneth Power?
Any update on the timeline Kenneth Power?
how many years has this been planned for? Here is the script: http://www.inmotionhosting.com/support/website/cpanel-account-management/split-single-cpanel-account-into-multiple-accounts-using-ssh
how many years has this been planned for? Here is the script: http://www.inmotionhosting.com/support/website/cpanel-account-management/split-single-cpanel-account-into-multiple-accounts-using-ssh
Any new when this tool will be launched ?
Regards,
Satta Matka
Any new when this tool will be launched ?
Regards,
Satta Matka
would love to know when this is going to be implemented its been far too long...
would love to know when this is going to be implemented its been far too long...
It's on hold until easy apache 4 comes out as they have made huge changes to the way domains are managed. I guess as it's in planned stage it will be one of the first things to be included in 11.52 as 11.50 will soon be released.
It's on hold until easy apache 4 comes out as they have made huge changes to the way domains are managed. I guess as it's in planned stage it will be one of the first things to be included in 11.52 as 11.50 will soon be released.
Moderators Note: This is not the place to promote third party services.
Moderators Note: This is not the place to promote third party services.
Looking Forward to the release of this :) Waiting in anticipation ...
Looking Forward to the release of this :) Waiting in anticipation ...
In searching the web, I find lots of users and threads where cPanel clients have been BEGGING for this feature over 5 YEARS now. Easy Apache or not, the users (read: PAYING CLIENTS) of cPanel pay a lot of money to use this software. No internal account migration tool after all these years of waiting is a shameful display of a blatant "lack of interest in customer service". I'm VERY disappointed that after all this time, a highly requested basic feature has STILL not been implemented.
In searching the web, I find lots of users and threads where cPanel clients have been BEGGING for this feature over 5 YEARS now. Easy Apache or not, the users (read: PAYING CLIENTS) of cPanel pay a lot of money to use this software. No internal account migration tool after all these years of waiting is a shameful display of a blatant "lack of interest in customer service". I'm VERY disappointed that after all this time, a highly requested basic feature has STILL not been implemented.
oops - double post
oops - double post
Our programmer did fix this in a couple of hours with programming using your API.
We have been using the script for many years now and it's working like a charm.
Strange that my programmer can fix this so easy, but cPanel cannot.
If you need to get something done, it's always best to do it yourself :-)
Our programmer did fix this in a couple of hours with programming using your API.
We have been using the script for many years now and it's working like a charm.
Strange that my programmer can fix this so easy, but cPanel cannot.
If you need to get something done, it's always best to do it yourself :-)
Now I found out why so many people double post (spam).
When I comment it's just "loading" and finally your comment does not show and push "Comment" again :p Sorry guys. Please fix cPanel!
Now I found out why so many people double post (spam).
When I comment it's just "loading" and finally your comment does not show and push "Comment" again :p Sorry guys. Please fix cPanel!
How would you expect mysql databases to be handled with this process?
How would you expect mysql databases to be handled with this process?
The migration tool would open a short form where you could select the already made new account that the add-on domain is migrating to so that the database name prefix can be updated along with ownership permissions, serialized data updates and probably more I am unaware of.
Again, this is less difficult than moving a bunch of sites at once with the existing "Transfer Tool" that can transfer between 2 foreign hosts in unrelated data centers.
The migration tool would open a short form where you could select the already made new account that the add-on domain is migrating to so that the database name prefix can be updated along with ownership permissions, serialized data updates and probably more I am unaware of.
Again, this is less difficult than moving a bunch of sites at once with the existing "Transfer Tool" that can transfer between 2 foreign hosts in unrelated data centers.
Hello,
Thank you all for your input on this item. We have been investigating a simple commandline tool as a first deliverable. The sticking point that we seem to keep hitting is how to be smart about the databases and database users.
We are currently thinking of letting the reseller select which databases and users go with which accounts. This get tricky when a db user is attached to more than one db. If one db is sent to the new account and another stays with the old account, then where does the user go?
We would likely use a backup file to do the addon account migration. This will prevent having to worry about data changing mid stream.
As far as converting an account to an addon domain. This idea would be better discussed in https://features.cpanel.net/topic/as-a-reseller-i-want-the-ability-to-easily-merge-multiple-cpanel-accounts-and-their-addonparked-domains-into-a-single-cpanel-account-so-that-i-can-easily-c
I would like to hear your input on the concept!
Thanks,
Travis Ellis
Hello,
Thank you all for your input on this item. We have been investigating a simple commandline tool as a first deliverable. The sticking point that we seem to keep hitting is how to be smart about the databases and database users.
We are currently thinking of letting the reseller select which databases and users go with which accounts. This get tricky when a db user is attached to more than one db. If one db is sent to the new account and another stays with the old account, then where does the user go?
We would likely use a backup file to do the addon account migration. This will prevent having to worry about data changing mid stream.
As far as converting an account to an addon domain. This idea would be better discussed in https://features.cpanel.net/topic/as-a-reseller-i-want-the-ability-to-easily-merge-multiple-cpanel-accounts-and-their-addonparked-domains-into-a-single-cpanel-account-so-that-i-can-easily-c
I would like to hear your input on the concept!
Thanks,
Travis Ellis
What would likely solve this would be to map databases to both usernames and domain names. But even with this, there will be issues. What if you manually move files between addon domain folders (i.e. /domain.com-test and /domain,com)...
What would likely solve this would be to map databases to both usernames and domain names. But even with this, there will be issues. What if you manually move files between addon domain folders (i.e. /domain.com-test and /domain,com)...
I'm not sure that databases should be migrated.
If they are, I would have a tool to select databases that need to be migrated.
You would select the databases that need to be migrated. These would then be created with the new username prefix if username prefixes are used, or otherwise a new name would be requested.
Once the migration is done all you would have to do is :
1) Rename databases in scipt config files
2) Delete the databases from the original account.
A message should clearly inform the user of the steps he has to do manually.
I think it would be wrong to delete existing databases or database users as a single database could be used by multiple scripts on multiple domains.
I'm not sure that databases should be migrated.
If they are, I would have a tool to select databases that need to be migrated.
You would select the databases that need to be migrated. These would then be created with the new username prefix if username prefixes are used, or otherwise a new name would be requested.
Once the migration is done all you would have to do is :
1) Rename databases in scipt config files
2) Delete the databases from the original account.
A message should clearly inform the user of the steps he has to do manually.
I think it would be wrong to delete existing databases or database users as a single database could be used by multiple scripts on multiple domains.
with regards to the database USer i would suggest that the migrated site is the one that would just need to recreate users and permissions for the the DB IF it exists on other databases in the main account and seems liginca since the db username MUST change anyway since they all contain the root username of the account, so that sort of thing would have to be edited updated manually, but thats way easier then the current process!
with regards to the database USer i would suggest that the migrated site is the one that would just need to recreate users and permissions for the the DB IF it exists on other databases in the main account and seems liginca since the db username MUST change anyway since they all contain the root username of the account, so that sort of thing would have to be edited updated manually, but thats way easier then the current process!
ok - i can do the database manually if necessary but please distribute something.
ok - i can do the database manually if necessary but please distribute something.
Heck, at this point (as one of the first users to request this over 5 years ago) I'd be happy even if I just had to handle exporting / importing / migrating the databases myself and have just a basic "Addon to Master cPanel" account changer, just to get *any* forward movement on this feature.
Heck, at this point (as one of the first users to request this over 5 years ago) I'd be happy even if I just had to handle exporting / importing / migrating the databases myself and have just a basic "Addon to Master cPanel" account changer, just to get *any* forward movement on this feature.
This tool already exist for years, maybe cPanel needs to buy this company and their programmer(s).
I used it more than once and it works. It's a shame cPanel doesn't have this standard.
http://admin-ahead.com/cPanel-Plugins/Add-On-Domain-to-Main-Account-Convertor-cPanel-WHM-Plugin.html
This tool already exist for years, maybe cPanel needs to buy this company and their programmer(s).
I used it more than once and it works. It's a shame cPanel doesn't have this standard.
http://admin-ahead.com/cPanel-Plugins/Add-On-Domain-to-Main-Account-Convertor-cPanel-WHM-Plugin.html
edit: doublepost
edit: doublepost
Hi, i see this idea has been shared 7 years ago, and has the status 'planned'. Is there an eta on this?
Hi, i see this idea has been shared 7 years ago, and has the status 'planned'. Is there an eta on this?
Any update. Needed this feature a few times.
Any update. Needed this feature a few times.
Seems that all the sarcastic posts, pointing out that cPanel is not taking this (or possibly all) feature requests serious, have been deleted. I just wanted to say - please keep them coming! I get an email with a copy each time, and it is encouraging to know there are quite a few people that would like to see cPanel create a much wanted feature. Also, it may make cPanel take this more serious, as they have to constantly delete posts that make fun of them.
cPanel - This feature would take a skilled programmer less than a week to create. If you do not have skilled programmers, or those that you do have are busy with other tasks, HIRE ME!
Seems that all the sarcastic posts, pointing out that cPanel is not taking this (or possibly all) feature requests serious, have been deleted. I just wanted to say - please keep them coming! I get an email with a copy each time, and it is encouraging to know there are quite a few people that would like to see cPanel create a much wanted feature. Also, it may make cPanel take this more serious, as they have to constantly delete posts that make fun of them.
cPanel - This feature would take a skilled programmer less than a week to create. If you do not have skilled programmers, or those that you do have are busy with other tasks, HIRE ME!
Convert Addon Domains into cPanel accounts? Why make that a Feature when it can be easily done via CLI.
ie. grep DNS /var/cpanel/users/* | grep -vE "DNS=|XDNS" | awk {'system("/scripts/wwwacct "$1" " substr($1,0,8) " staticpassword ")'}
Convert Addon Domains into cPanel accounts? Why make that a Feature when it can be easily done via CLI.
ie. grep DNS /var/cpanel/users/* | grep -vE "DNS=|XDNS" | awk {'system("/scripts/wwwacct "$1" " substr($1,0,8) " staticpassword ")'}
Dylan, the feature request section has a bug since a few years, which makes it appear as if the post has not been submitted, and clicking Comment more than once will submit your post more than once. It was pointed out by Morton in this thread a few weeks ago.
To answer your question: Because that piece of code wouldn't do all that is required. A few examples: Most Addon domain have their own email accounts, so they need to be transferred, as well as forwarders. The databases that are used by the addon would have to be transferred into the new account, and then they'd have to get new names with the new cpanel user prefix, and new database users with the correct cpanel user prefix would have to be created.There may be cron jobs related to the addon.The DNS Zone for the addon has to be removed from the original account, so it can be created/owned by the new one.
There are quite a few things to consider when changing an Addon to a cpanel account, however, it's no rocket science and the feature should have been developed by now.
Dylan, the feature request section has a bug since a few years, which makes it appear as if the post has not been submitted, and clicking Comment more than once will submit your post more than once. It was pointed out by Morton in this thread a few weeks ago.
To answer your question: Because that piece of code wouldn't do all that is required. A few examples: Most Addon domain have their own email accounts, so they need to be transferred, as well as forwarders. The databases that are used by the addon would have to be transferred into the new account, and then they'd have to get new names with the new cpanel user prefix, and new database users with the correct cpanel user prefix would have to be created.There may be cron jobs related to the addon.The DNS Zone for the addon has to be removed from the original account, so it can be created/owned by the new one.
There are quite a few things to consider when changing an Addon to a cpanel account, however, it's no rocket science and the feature should have been developed by now.
Fair enough - point taken. I see my multiple comments. Whoops!
Fair enough - point taken. I see my multiple comments. Whoops!
Hi everyone,
Sorry for the noise with the fraudulent accounts. We have had a user register multiple accounts with different throwaway email accounts. We know it was the same users considering they all used the same IP address to connect with.
This feature is something we have plans of working on. We have an idea of how to get this done. But the team that would do it is busy working on Two-Factor Auth. We can provide a simple script that would do the migration, it would have to handle the issues of Databases without clobbering anything. It would pull from a cPanel Backup file to do the migration. This will prevent files from changing during the migration.
Thank you for your continued patience,
Travis
Hi everyone,
Sorry for the noise with the fraudulent accounts. We have had a user register multiple accounts with different throwaway email accounts. We know it was the same users considering they all used the same IP address to connect with.
This feature is something we have plans of working on. We have an idea of how to get this done. But the team that would do it is busy working on Two-Factor Auth. We can provide a simple script that would do the migration, it would have to handle the issues of Databases without clobbering anything. It would pull from a cPanel Backup file to do the migration. This will prevent files from changing during the migration.
Thank you for your continued patience,
Travis
You will have to manually edit the configuration file with the new database name and user of the transferred addon domain that will exist as its own cPanel account. You will also have to manually edit any other configuration files where the file paths may need to be updated. This tool can cause extended downtime for a site if clients do not know how to update their configuration files.
You will have to manually edit the configuration file with the new database name and user of the transferred addon domain that will exist as its own cPanel account. You will also have to manually edit any other configuration files where the file paths may need to be updated. This tool can cause extended downtime for a site if clients do not know how to update their configuration files.
Wow this feature is now In progress. Congratulations to cPanel team.
Wow this feature is now In progress. Congratulations to cPanel team.
Nice to see it is In Progress. I will be following up this one.
Nice to see it is In Progress. I will be following up this one.
Me too. Then I can un-install a third party addon I have. Also please add this feature with an API hook so that we can use it via WHMCS.
Me too. Then I can un-install a third party addon I have. Also please add this feature with an API hook so that we can use it via WHMCS.
Me 44too (#442). Need this feature, it's very annoying to not be able to add the domain to another place even if inactive due to "error already exists".
I only hope you release it BEFORE you terminate the x3 theme because if you do that I will never get this feature because I'll never upgrade cpanel to a version in which does not allow you to use the x3 theme.
Me 44too (#442). Need this feature, it's very annoying to not be able to add the domain to another place even if inactive due to "error already exists".
I only hope you release it BEFORE you terminate the x3 theme because if you do that I will never get this feature because I'll never upgrade cpanel to a version in which does not allow you to use the x3 theme.
Will look for this feature rolling out, It's Really really useful according to me when we have to create new from addon domain.
Will look for this feature rolling out, It's Really really useful according to me when we have to create new from addon domain.
Looking very much forward to this feature becoming a realization. I only wonder if it will be compatible with CloudLinux 6.7 and EasyApache 3, since currently CL 6.x is not compatible with EA4.
Looking very much forward to this feature becoming a realization. I only wonder if it will be compatible with CloudLinux 6.7 and EasyApache 3, since currently CL 6.x is not compatible with EA4.
Cloudlinux 6 currently has a beta version of EA4 compatibility so it shouldn't be too long now.
https://cloudlinux.com/blog/entry/beta-easyapache-4-released-for-cloudlinux
Cloudlinux 6 currently has a beta version of EA4 compatibility so it shouldn't be too long now.
https://cloudlinux.com/blog/entry/beta-easyapache-4-released-for-cloudlinux
so this is just for cloudlnux? I certainly hope not.
so this is just for cloudlnux? I certainly hope not.
Definitely not! It will be part of v56 on all of our supported operating systems. In case you want a quick look, I posted a tiny video to twitter yesterday, that gives a basic overview of its operation: https://twitter.com/cpaneldev/status/712024671433011200
Definitely not! It will be part of v56 on all of our supported operating systems. In case you want a quick look, I posted a tiny video to twitter yesterday, that gives a basic overview of its operation: https://twitter.com/cpaneldev/status/712024671433011200
I hope it can also move conf files from /usr/local/apache/conf/userdata/..... from the old to the new path
I hope it can also move conf files from /usr/local/apache/conf/userdata/..... from the old to the new path
I still don't understand how this will work without having to update site configuration files manually? For example, a WordPress site with a database called cpanel1_wrdp is an addon domain. The addon domain is then set up as its own cPanel account called cpanel2. The database is copied over to the new cPanel account and the database now becomes cpanel2_wrdp. The wp-config.php file will manually need to be updated with the new database name, correct? Similarly, in a Joomla configuration file, the following is specified:
public $log_path = '/home/cpanel1/addondomain/log';
public $tmp_path = '/home/cpanel1/addondomain/tmp';
If an addon domain is moved to a new account called cpanel2 then the above file paths need to be changed in the Joomla configuration file (along with the database name) otherwise the site will not come up. Surely not everyone will realize they will be required to update these config files. Does this not have disaster written all over it? Here is my addon to cPanel account guideline:
Addon domain turned into a separate cPanel1. Download the content of your addon domain to your local PC.2. Backup any associated database(s).3. Go into the original cPanel and remove the addon domain from under the Addon Domains icon. (You do not need to delete the original content or original databases.)4. Create a New Account inside your WHM. Fill out the form, using the old addon domain name as the Domain. Click the Create button.5. Once the new cPanel is ready, upload the content of your old addon domain to this new cPanel, in the public_html folder. (When using FTP to upload, connect to the cPanel's IP address and login with the new cPanel's username and password.)6. Login to the new cPanel and restore the database backup(s).7. Reconfigure any database connections. (The database name and username have likely changed.)Your site will only be down as long as it takes to complete these steps. No need to change your name servers.
I still don't understand how this will work without having to update site configuration files manually? For example, a WordPress site with a database called cpanel1_wrdp is an addon domain. The addon domain is then set up as its own cPanel account called cpanel2. The database is copied over to the new cPanel account and the database now becomes cpanel2_wrdp. The wp-config.php file will manually need to be updated with the new database name, correct? Similarly, in a Joomla configuration file, the following is specified:
public $log_path = '/home/cpanel1/addondomain/log';
public $tmp_path = '/home/cpanel1/addondomain/tmp';
If an addon domain is moved to a new account called cpanel2 then the above file paths need to be changed in the Joomla configuration file (along with the database name) otherwise the site will not come up. Surely not everyone will realize they will be required to update these config files. Does this not have disaster written all over it? Here is my addon to cPanel account guideline:
Addon domain turned into a separate cPanel1. Download the content of your addon domain to your local PC.2. Backup any associated database(s).3. Go into the original cPanel and remove the addon domain from under the Addon Domains icon. (You do not need to delete the original content or original databases.)4. Create a New Account inside your WHM. Fill out the form, using the old addon domain name as the Domain. Click the Create button.5. Once the new cPanel is ready, upload the content of your old addon domain to this new cPanel, in the public_html folder. (When using FTP to upload, connect to the cPanel's IP address and login with the new cPanel's username and password.)6. Login to the new cPanel and restore the database backup(s).7. Reconfigure any database connections. (The database name and username have likely changed.)Your site will only be down as long as it takes to complete these steps. No need to change your name servers.
This feature is confirmed as part of cPanel & WHM version 56 which will go to CURRENT as soon as next week. You can find a quick previous on the cPanelDev twitter account:
https://twitter.com/cpaneldev/status/712024671433011200
This feature is confirmed as part of cPanel & WHM version 56 which will go to CURRENT as soon as next week. You can find a quick previous on the cPanelDev twitter account:
https://twitter.com/cpaneldev/status/712024671433011200
https://documentation.cpanel.net/display/ALD/Convert+Addon+Domain+to+Account
This feature is included in cPanel & WHM version 56 as a first iteration. That means that we are not completely done with development for the feature. We will continue working on this for 58 to more round out our feature. I have included a list of things we are converting and things that we have not yet gotten to. Thanks eveyone for your support.
Data migrated
The Convert Addon Domain to Account feature allows users to migrate the following data:
Data not migrated
The Convert Addon Domain to Account feature does not allow users to migrate the following data:
This is available in cPanel & WHM version 56. Comments are now locked, but if you require any assistance you can open a ticket with our support team, email benny (benny@cpanel.net) or ask on twitter (@cpaneldev).
https://documentation.cpanel.net/display/ALD/Convert+Addon+Domain+to+Account
This feature is included in cPanel & WHM version 56 as a first iteration. That means that we are not completely done with development for the feature. We will continue working on this for 58 to more round out our feature. I have included a list of things we are converting and things that we have not yet gotten to. Thanks eveyone for your support.
Data migrated
The Convert Addon Domain to Account feature allows users to migrate the following data:
Data not migrated
The Convert Addon Domain to Account feature does not allow users to migrate the following data:
This is available in cPanel & WHM version 56. Comments are now locked, but if you require any assistance you can open a ticket with our support team, email benny (benny@cpanel.net) or ask on twitter (@cpaneldev).
The scope of this feature has been increased in cPanel & WHM version 58, which was just released to the CURRENT tier. You can read about the update in the release notes.
The scope of this feature has been increased in cPanel & WHM version 58, which was just released to the CURRENT tier. You can read about the update in the release notes.
Replies have been locked on this page!