Skip to Content
Browse documentation

Add a Hosting Package in WAP

Configure all hosting package resources, outgoing email policy, feature access and conditional CloudLinux controls before creating an Eenos package.

Open Hosting → Packages → Add Package. Use administrator WAP access over HTTPS with JavaScript for conditional controls and confirmation. Demo sessions cannot create packages.

General Package Information

FieldValue and validation
Package NameRequired unique name, maximum 200 characters; letters, digits, hyphen and underscore.
Disk Space Quota (MB)Unlimited or custom numeric disk allocation.
Bandwidth Limit (MB)Unlimited or custom numeric bandwidth allocation.
FTP AccountsUnlimited or numeric FTP-account count.
Email AccountsUnlimited or numeric mailbox count.
Quota per Email Address (MB)Unlimited or numeric mailbox allocation.
Mailing ListsUnlimited or numeric mailing-list count.
SQL DatabasesUnlimited or numeric database count.
Sub DomainsUnlimited or numeric subdomain allowance.
Parked DomainsUnlimited or numeric parked-domain allowance.
Addon DomainsUnlimited or numeric addon-domain allowance.
Dedicated IPRequired Yes/No allocation policy; actual allocation depends on inventory and the provisioning workflow.
Shell AccessRequired Yes/No policy; review the account creation/plan-change workflow's actual shell behavior.
Select Feature ListRequired feature-list reference. Create Feature opens its separate tool.

The resource fields require a value and accept the unlimited marker or numeric values. Review actual capacity and service availability rather than assuming a valid number is operationally suitable. Feature names use letters, digits, underscores and hyphens; choose an intended existing list from the interface.

Outgoing Email Limits

Outgoing recipients per domain per hour accepts a positive whole number. Maximum failed/deferred delivery percentage accepts 1–100. Both support Unlimited / Inherit or Custom.

Inherit follows server limits; it is not an override that bypasses global ceilings. Custom values must fit the server policy. An unreadable server email-ceiling policy prevents validation. These fields govern sending policy, not mailbox storage.

CloudLinux controls

The CloudLinux section depends on installed tooling; the save handler stores CloudLinux-specific configuration when CloudLinux is detected. It does not install or license CloudLinux.

ControlMeaning
Enable CageFSEnabled/disabled account isolation preference; application fallback is enabled. This is separate from Enable LVE.
Enable LVEEnable resource-control configuration.
SPEEDCPU percentage; 100% represents one core.
Memory (RAM) / VMEMPhysical/virtual memory limits in MB.
Max Entry Proc / NprocEntry-process and process-count limits.
Disk IOThroughput in KB/s.
Disk IOPSOperations per second.
Inode Soft Limit / Inode Hard LimitFile/directory-count limits.
MySQL CPU LimitDatabase CPU percentage.
MySQL I/O LimitCombined database read/write limit in MB/s.

LVE numeric fields use Default or a custom whole number of at most 18 digits. Blank custom values are invalid when validated. If both inode limits are numeric and the hard limit is positive, soft cannot exceed hard. CPU speed cannot exceed logical CPU count × 100; RAM/VMEM cannot exceed detected system memory.

MySQL Governor must be installed and enabled for database-limit enforcement. CageFS, LVE and Governor settings are configuration requests, not guarantees that every subsystem is active. Default values are not the same as unlimited capacity.

Create and verify

  1. Choose a unique name and review all resource fields.
  2. Select the feature list, dedicated-IP and shell policies.
  3. Review email inheritance/custom limits and any CloudLinux settings.
  4. Select Create Package, review the creation confirmation and confirm, or cancel.
  5. Look for the named package-created success message.
  6. Open All Packages and verify the definition before using it for an account.

The view writes a package definition with the current administrator session as owner and records a package audit event. It does not create a hosting account or reserve all resources specified by the package.

Errors, recovery and precautions

Duplicate names, invalid names, missing values, invalid numeric/default choices, excessive email ceilings and inconsistent inode limits require correction. Form submissions preserve entered controls for review.

Directory preparation, writes or file-ownership updates can fail. A message that a file was created but ownership could not be updated means partial creation, not a safe invitation to submit the same name again. Inspect All Packages and server-side errors before retrying.

  • Do review capacity, feature dependencies and enforcement prerequisites.
  • Do verify the stored package before customer use.
  • Do not interpret Unlimited, Default or a saved checkbox as verified resource availability.
  • Do not assume package creation provisions accounts.

Previous: All Packages. Related workflow: Edit Package.