Skip to Content
Browse documentation

Upgrade or Downgrade a Hosting Account

Assign an existing Eenos hosting package to an account, review resource and feature changes, and verify plan-change results.

Open Hosting → User Accounts → Upgrade or Downgrade to assign another existing hosting package. This changes one account's plan; it does not edit the package definition for all customers.

Before you begin

Use administrator WAP access over HTTPS with JavaScript enabled. Demo submissions are blocked. Review current usage, feature dependencies and any account-specific overrides before changing plans. The table disables plan changes for suspended accounts; review suspension separately rather than assuming this tool will unsuspend them.

Table and fields

The table displays User, Domain, Current Plan, Status and Action, with search and pagination. Create Plan opens package creation separately.

Dialog fieldMeaning
Hosting AccountRead-only target username.
DomainRead-only primary domain.
Current PlanExisting package.
New Hosting PlanRequired existing package selected from the available list.

The new-plan selector starts with a prompt, not an automatically chosen replacement. The server checks that the account and selected package exist.

Change the plan

  1. Select Change Hosting Plan for the intended account.
  2. Review its identity and Current Plan.
  3. Select New Hosting Plan and review the Plan update notice.
  4. Select Change Plan, or cancel.
  5. Look for User Hosting Plan changed successfully with the username and package.
  6. Reload and verify the plan, limits, features and affected customer functionality.

The helper copies package resource/feature values into account data, sets the package name and applies disk quota. Existing dedicated-IP and shell settings are excluded from this package-copy operation; do not expect a plan change alone to allocate a new IP or change shell access.

Outgoing email limits from the new package are normalized; missing fields in older packages become inherited limits rather than preserving the previous plan's values. CloudLinux settings may be updated or removed according to package data, with applicable LVE application attempted when tooling is installed. A plan-save success does not independently verify all LVE effects.

Review reductions and account overrides

A downgrade can reduce limits or remove required features. Plan assignment can replace account-specific resource values. Record the previous plan and overrides, review current usage, and verify the resulting account rather than relying only on the package name.

Errors and recovery

Missing/nonexistent packages, invalid accounts or invalid package email settings can prevent a change. A server-side write/operation failure may leave partial state. Review actual account data, quota and logs before retrying. Demo sessions cannot apply the operation.

Reassigning the previous plan restores that plan's values; it is not guaranteed to restore prior custom overrides or every downstream effect. Record and restore such settings separately through Modify Account.

Do’s and don’ts

  • Do check resource usage and required features before downgrading.
  • Do verify account overrides, quota and applicable CloudLinux limits afterwards.
  • Do not treat a plan change as IP migration, password reset or shell-management action.
  • Do not edit a shared package when the intended change is only for one account.

Previous: Change Password. Next: Make Reseller.