Skip to content

Knowledgebase

Creating a Webuzo hosting package and user

control-panels, servers

Create a Webuzo plan and feature set before provisioning repeatable hosting accounts. A plan controls allocated resources, while feature settings determine which tools are available. Keeping these decisions explicit makes later customer support and capacity planning easier.

Check access and requirements

Use an authorized administrator or reseller account. Define the intended disk, inode, bandwidth, database, mailbox and domain allowances. Confirm the reseller allocation and actual server capacity. Decide whether shell, cron and any reseller privileges belong in this specific service.

01 Create a Webuzo hosting package and user

  1. Open Plans > Add Plan and give the plan an identifiable name. Set the resource limits and save the definition.
  2. Review or create the appropriate Feature Set. Enable only the customer tools the service supports and ensure essential backup or security access is not accidentally hidden.
  3. Open Users > Create New Account. Enter the primary domain, account username, contact information and a unique strong credential through the secure form.
  4. Choose the saved plan or deliberately configure custom limits. Review dedicated IP choices and leave Make Reseller disabled for an ordinary hosting user.
  5. Check shell access and cron permissions, then select the intended feature set and save the user. Avoid granting server-level access to solve a normal website deployment requirement.
  6. Open the created account details and record the effective limits, IP and owner. Provide access through your normal secure onboarding process without exposing the password in public messages.

Does a plan reserve physical server resources?

Plan limits define account allocations and enforcement. They do not create additional RAM, disk performance or storage, so administrators must still monitor host capacity and customer usage.

Confirm the expected result

Use an authorized end-user session to check the expected tools and primary website. Confirm the account can create permitted resources and cannot reach another account data. Verify the primary domain DNS and include the account in the backup policy.

Resolve setup problems

If creation fails, check duplicate usernames or domains, licensing and remaining resource allowance. Inspect the error before retrying because a partially created resource may already exist. If the wrong privileges were assigned, correct the account directly rather than deleting a populated account.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support