Suspension temporarily restricts a DirectAdmin account without deleting its stored website and mailbox data. Use it for an authorized billing, resource or security action, and record why it happened so reinstatement addresses the actual cause.
IN THIS ARTICLE
Prepare for the change
Confirm the exact username and owner. Distinguish a single user from a reseller or administrator because the affected scope can differ. Preserve evidence for a suspected compromise, check backup status, and arrange appropriate customer communication through your established process.
01 Suspend and reinstate a DirectAdmin user safely
- Open the authorized List Users or Show All Users page and identify the account by username and domain.
- Inspect current suspension state, recorded reason and usage. If the account is automatically suspended for a limit, determine which limit triggered the action.
- Select only the intended user and choose Suspend. Confirm the action after checking the selection count.
- Verify the expected account and website restriction. Also inspect relevant mail and scheduled-task behaviour for your server configuration; do not assume suspension contains every possible compromised process.
- Before choosing Unsuspend, resolve the billing or resource condition, or complete the necessary security cleanup and credential rotation. Reinstate the exact user and monitor it.
Does suspension remove a compromised file?
No. Treat suspension as one containment action. The malicious content, stolen credentials and scheduled persistence must be investigated and repaired before service is restored.
Confirm the expected result
Confirm the intended user state in the panel and test the public website. After reinstatement, test login and a controlled mail operation, then check whether automatic enforcement immediately suspends the account again.
If the change does not work
If a user remains unavailable after reinstatement, inspect suspension reasons, DNS, service logs and application failures separately. Do not delete and recreate the account to clear a suspension. If a reseller-level action affected more users than intended, restore access carefully according to the recorded ownership and incident scope.