CloudLinux Manager (formerly LVE Manager) is where the server administrator decides how much CPU, memory, I/O and processes each account may use. Good defaults keep the server fast for everyone without causing constant 508 errors.
On MdmHost reseller and master reseller plans this is already done for you. This guide is for administrators of their own cPanel VPS or dedicated server with root access.
Before you start
- CloudLinux installed (see installing CloudLinux).
- Root access to WHM.
- An idea of your server size: cores, RAM and disk type.
Set server-wide default limits
- Open WHM → Plugins → CloudLinux Manager.
- Go to Users (or Packages) and edit the Default limits.
- Typical shared-hosting starting values:
| Limit | Starting value |
|---|---|
| SPEED (CPU) | 100% (one core) |
| PMEM (physical memory) | 1 GB |
| IO | 2–5 MB/s on SSD/NVMe |
| IOPS | 1024 |
| EP (entry processes) | 20–30 |
| NPROC | 100 |
Each limit is explained for users in CloudLinux limits explained.
Set limits per package
- Open the Packages tab.
- Edit each WHM package and give bigger plans higher limits.
- Accounts follow their package automatically, including new accounts.
Tip: Set limits on packages, not on individual users. Per-user overrides are hard to track and are lost track of when accounts move between packages.
Enable reseller limits
Reseller limits give each reseller a total pool, which they divide among their customers in their own CloudLinux Manager.
- Go to Users, find the reseller and enable Reseller limits.
- Set the reseller's total CPU, memory, I/O, EP and NPROC.
- The reseller then manages their customers' limits (see reseller guide to CloudLinux Manager).
Notifications and options
- In Options, enable fault notifications for admins, resellers and users, with sensible thresholds so nobody is flooded.
- Choose whether users see Resource Usage in cPanel (recommended; see Resource Usage for users).
- In Selectors, choose the default PHP version, available versions and extensions, and enable Node.js and Python selectors if you offer them.
Watch and adjust
After a week, review Historical Usage and sort by faults. Accounts with constant faults need optimisation or a bigger plan; if almost every account faults, your defaults are too tight. The user-side fix list is in fixing 508 errors.
Troubleshooting
Limits do not apply to an account
The user has an individual override. Reset it to the package default.
Statistics are empty
Check that the lvestats service is running: systemctl status lvestats.
Frequently asked questions
Should I set limits close to the server total?
No. Limits are maximums per account, and most accounts are idle most of the time. Overcommitting is normal; tight limits only cause errors.
Do limits affect cron jobs and SSH?
Yes. All processes of the user run inside its LVE, including cron jobs and shell sessions.
How do I give one customer temporary extra resources?
Set a user-level override for a limited time, note it, and remove it afterwards so the account returns to its package limits.
What happens when a reseller pool is full?
The reseller's customers share the pool. When it is exhausted they are slowed or get 508 errors, so size reseller pools with headroom.