Here’s one example (including an example warning that is normal in our testing environment): Logs for each conversion are stored on the server and are viewable in the same WHM interface. Once the addon domain has been converted to its own cPanel account, you will now see the start and end times of the completed addon conversion: This will allow for the Convert tool to move both the database and user for the selected addon domain. If you want to move or copy either or both of these options, please make sure to click the checkbox under the Database and User sections. When clicking on the “Configure” button for MySQL databases, you’ll see the screen above, with the option to either move or copy your MySQL databases and users. One of the more helpful features of Converting Addon domains to their own accounts includes the ability to move MySQL databases and users, as shown in the following screenshot: You will then be taken to a second interface where you are allowed to choose the new username, define the new account’s package, and a slew of other options.
Once you locate the domain you want to extract, click “Convert.” Use the search box at the top of the list to reduce the number of displayed domains, or click the navigation buttons along the bottom to scroll through all the addon domains. You will then be presented with a list of Addon domains and their associated cPanel account username. Once you’re logged in to WHM, choose the “Convert Addon Domain to Account” tool from the sidebar.
Cpanel whm account creator how to#
In the following blog post, we will show you exactly how to accomplish this! Users with root-level access or resellers with the “ Rearrange Accounts” Privilege will have access to move an addon domain into its own separate cPanel account. There may be certain circumstances or occasions where you will want to split off an addon domain into its own cPanel account. In the blog post “ Managing Multiple Domains from a Single Hosting Account,” we explain how to manage different domains you may own in a single cPanel hosting account. It has been updated for accuracy, and readability. To check whether the user already exists, perform either of the following steps:Īttempt to navigate to the /home/username directory, where username represents the account username.Ĭheck the contents of the /etc/passwd directory for an entry for that user.This post was originally added to our blog on Aug 18th, 2016. If the system returns an unable to add the user error, the user may already exist in your system. If they exist, delete the /etc/grshadow.lock and /etc/group.lock files.
To rebuild the file, run the grpconv command. To move the existing /etc/gshadow file, run the following command: mv /etc/gshadow /etc/rrupt To rebuild corrupt files, perform the following steps: Any /etc/gshadow file that does not include these lines is corrupt. For each group in the /etc/groups file, the /etc/gshadow file should include a line in the groupname::: format, where groupname represents the group name. If the /etc/gshadow file becomes corrupt, the system cannot correctly add the account to your server. To remove this flag, run the following commands: chattr -i /etc/passwd If these files contain the immutable flag, they will return i in these commands’ output. To check these files, run the following commands: lsattr /etc/group
If the /etc/passwd or /etc/group files contain the immutable flag, the system cannot edit them and therefore cannot add the account to your server. You may receive this error for several reasons: Immutable files For more information about account creation, read our Create a New Account documentation.
0 kommentar(er)
