This document explains the differences between account suspension, bandwidth limiting, and account termination. This document also describes why you might terminate an account or suspend an account.
The system does not automatically initiate account suspension.
When you suspend an account, the system imposes several limitations that remain in place until you unsuspend the account. You may wish to suspend an account for the following reasons:
- A user fails to comply with your terms of service.
- A user did not pay their bill for service.
Suspend or unsuspend an account
To suspend or unsuspend an account, use one of the following methods:
- WHM's Manage Account Suspension interface (Home >> Account Functions >> Manage Account Suspension).
- From the command line, run either of the following scripts:
/usr/local/cpanel/scripts/suspendacct— Suspends an account
/usr/local/cpanel/scripts/unsuspendacct— Unsuspends an account.
If you suspend an account, the following statements are true:
- The account's
cpuserfile contains the
/usr/local/apache/conf/includes/account_suspensions.conffile contains a Virtual Host include for the user.
This file contains a
RedirectMatchdirective that redirects website traffic for the user's account to an account suspension page. This directive resembles the following example:
- The system prepends the account's password hash in the
/etc/proftpd/usernamefiles with two exclamation points (
/var/cpanel/suspended/userfile contains a reason for suspension or the account's previous shell location.
The system places
*LOCKED*entries around the password entries in the mail user's
/home/user/etc/example.com/shadowfile, for example:
- The system allows email delivery and forwarding in addition to DNS queries.
For more information about the effects of account suspension, read our What Happens When You Suspend an Account documentation.
The system can initiate temporary limits automatically for accounts that exceed the monthly bandwidth limit. The system removes the limits automatically at the beginning of each month, when the account no longer exceeds the limit.
If the system imposes account limitations due to bandwidth limiting, the following statements are true:
- The Disk Used value is higher than the Disk Limit setting in WHM's View Bandwidth Usage interface (Home >> Account Functions >> View Bandwidth Usage).
./domainfiles that correspond to the account.
Remove bandwidth limitations
To remove these limitations before the end of a month, use one of the following methods to raise the monthly bandwidth limit:
Increase the bandwidth limit for a single user in WHM's Limit Bandwidth Usage interface (Home >> Account Functions >> Limit Bandwidth Usage).
- Increase the Monthly Bandwidth Limit setting for all of a package's users in WHM's Edit a Package interface (Home >> Packages >> Edit a Package).
Increase the Monthly Bandwidth Limit setting for a single user in WHM's Modify an Account interface (Home >> Account Functions >> Modify an Account).
Changes to this setting may trigger a package conflict. For more information, read our Modify an Account documentation.
- To remove the limitations for all of the accounts on your server with exceeded monthly bandwidth limits, use WHM's Unsuspend Bandwidth Exceeders interface (Home >> Account Functions >> Unsuspend Bandwidth Exceeders).
When you terminate an account, the system permanently deletes all of its data from the server. You may wish to terminate an account for the following reasons:
- You moved an account from one server to another server and all of the first server's information properly transferred..
- A user has not paid their bill for service for a significant period of time.
Terminate an account
To terminate an account, use one of the following methods:
- WHM's Terminate Accounts interface (Home >> Multi Account Functions >> Terminate Accounts).
/usr/local/cpanel/scripts/removeacctscript via the command line as the
If you terminate an account, the following statements are true:
- You cannot immediately recreate the account, because the system must remove the account's MySQL® users.
The system deletes the account's DNS zones by default.
You can choose to keep the account's DNS zone. This is useful, for example, when you need to move the account to a different server that belongs in the same DNS cluster.