What Happens When You Suspend an Account
Last modified: October 27, 2020
This document describes the actions that the system performs when you suspend an account.
To suspend or unsuspend an account, use WHM’s Manage Account Suspension interface (WHM >> Home >> Account Functions >> Manage Account Suspension).
Effects of suspension
The following table describes the actions that the system performs when you suspend an account and the limitations that result from these actions:
userrepresents the account’s username.
Adds suspended flags
The system adds the
SUSPENDTIME=epochdate flags to the account’s
/var/cpanel/users/cpuser file, where
epochdate represents the Unix time at which you suspended the account.
As a result, the appropriate WHM interfaces sets the account to
suspended and list the reason for suspension.
Locks reseller control
If you select the Prevent resellers from unsuspending checkbox when you suspend the account, the system touches the
As a result, the appropriate WHM interfaces sets the account to locked. The system does not allow resellers to unsuspend the account.
rootuser to unsuspend the account.
Stops all user processes
The system stops all of the processes that that account owns.
As a result, the system stops any functions that the cPanel account currently performs as the logged-in user. The following list includes some of the effects that this action may cause:
The system forcibly logs the user out of a current session.
The system stops the user’s cron jobs.
Locks mailing lists
The system creates a
suspended.lists directory in Mailman and moves the files for each of the account’s mailing lists to this directory.
As a result, the account’s mailing lists no longer function.
Locks Web Disk
The system creates a
/etc/webdav/shadow directory in the user’s
As a result, the account’s Web Disk accounts no longer function.
Locks email passwords
The system adds
LOCKED string to the
/etc/shadow password files for all of the account’s email users.
As a result, the account’s email users cannot download mail.
Stops mail transfer
The system no longer allows the account’s users to send email through the mail server.
Also, the mail server will force all mail currently in the outbound message queue from that account’s users to fail.
As a result, the account’s email users cannot send mail, and any mail they had in the mail server queue will fail.
Updates the Apache configuration files
The system updates Apache’s
httpd.conf file with a Virtual Host include file for the user.
The system creates the include file at the following location:
This include file contains a
RedirectMatchrule that redirects website traffic to the default template for suspended accounts.Note:
httpd.confinclude files originate from the following lines in Apache’s
1 2 3
[% IF file_test('f', '/usr/local/apache/conf/includes/account_suspensions.conf') -%] Include "/usr/local/apache/conf/includes/account_suspensions.conf" [% END -%]
As a result, visitors cannot access the account’s websites. Instead, a message appears that states the account was suspended.
To edit the message that appears for a suspended account’s sites, use WHM’s Web Template Editor interface (WHM >> Home >> Account Functions >> Web Template Editor).
Locks the shadow password
The system uses the
passwd -l command to lock the account’s
/etc/shadow password file. This command prepends the account’s passwords with two exclamation marks (
The following list includes some of the effects that this action causes:
The user cannot log in to their cPanel account.
The account’s database users cannot log in to their databases.
The suspended account’s password cannot change.
Modifies permissions of ftp directory
The system modifies the permissions of the user’s
public_ftp directory to
The system then creates the
/etc/proftpd/user.suspended file and locks the account’s FTP passwords in the
/etc/proftpd/user password files. Finally, the system prepends the account’s FTP passwords with two exclamation marks (
As a result, The account’s FTP users cannot log in to the FTP server.
Also, the system cannot back up the user’s
public_ftp directory because of the restrictive file permissions.
Changes MySQL user passwords
The system changes all of the MySQL users’ passwords. As a result, MySQL users cannot access their databases.