WHM’s Reset Account Bandwidth Limit restores an account’s allowance to its package default. It does not erase measured traffic or start a new billing month, so first determine whether the problem is an incorrect limit or unexpectedly high usage.
IN THIS ARTICLE
Prepare for the change
Record current usage, the account-specific allowance and the package allowance. Compare the customer’s authorised service and investigate any unusual traffic before increasing limits.
01 Restore a WHM bandwidth allowance without resetting usage
- Open the relevant bandwidth usage report and identify the account and period. Review the traffic source with the account owner if usage is unexpectedly high.
- If an account-specific exception should end, open Reset Account Bandwidth Limit and locate the account whose allowance differs from its package.
- Check the displayed package value, then choose Reset to Package Bandwidth Limit only when that is the intended result.
- For a different authorised allowance, use the supported Limit Bandwidth Usage or package-change workflow instead.
- Recheck the effective allowance and service state. Monitor usage after addressing the identified traffic source.
Confirm the expected result
The configured bandwidth allowance should match the intended plan or documented exception. Historical usage should remain meaningful for troubleshooting and capacity planning.
If the change does not work
If the account is absent from the reset screen, its allowance may already match the package. Do not delete traffic logs or alter statistics files to conceal a limit breach. If normal demand exceeds the plan, arrange a suitable capacity change.
Will resetting the limit clear this month’s usage?
No. The action concerns the allowed quota. Usage counters and billing-period handling are separate, and the service’s normal accounting remains applicable.
.png)
 (1).jpg)
 (1) (1).png)
 (1).png)
.jpg)
.jpg)
 (1).jpg)
.jpg)
