Managing a Hosting Account

Managing a single hosting account in vWHM.

The account management screen (vWHM → Accounts → click a username) is where you do everything to one hosting account. It is a stack of cards, each independent — every card is its own form, so saving one never touches another. The heading shows the username, a status pill (active or suspended), the primary domain and the creation date.

Almost every action here is written to the audit log with the account as its target.

Plan and usage

Shows the assigned package, live disk usage (measured on page load, so this card is what makes the page take a moment), and database and subdomain counts against their plan limits. A limit of 0 reads as "unlimited".

Change package applies a different package immediately, or clears it back to unlimited. Nothing is migrated or deleted — only the ceilings change. An account already over a newly-applied limit keeps everything it has; it simply cannot create more. See Packages and plans.

Login and password

Shows the username, a copy button, and the account's panel login URL.

Reset password sets a new password of at least 8 characters. The Generate button produces an 18-character password. The new password is shown in plain text in the confirmation message so you can pass it to the account owner. vWHM keeps no readable copy of it afterwards, so if you lose it, reset it again.

One reset updates three things at once:

• the system/SSH password (also used for SFTP and FTP)
• the panel login, which also bumps the account's session epoch, signing out every existing vPanel session for that account
• every mailbox password on the account, if the checkbox is left ticked (it is ticked by default)

If one of the three fails, the message tells you which parts succeeded and which did not, and still shows the new password.

PHP version

Sets the PHP version for this account's sites. The dropdown lists every PHP-FPM version installed on the server, plus Server default (mod_php).

Choosing a version moves the account into its own PHP-FPM pool running as its own Linux user. Choosing the server default reverts it to shared mod_php. The account can also change this from its own panel. If no PHP-FPM version is installed the card tells you so and suggests installing one. See PHP versions and account isolation.

Actions: suspend, unsuspend, terminate

Suspend locks the Linux password, sets the login shell to nologin, and disables the account's Apache vhost (with a config test before the reload). A suspended account cannot sign in to vPanel at all, cannot log in over SSH, and its websites stop being served. Its files, databases and mail data are all untouched.

Unsuspend reverses every step: unlocks the password, restores /bin/bash, and re-enables the vhost.

Terminate permanently deletes the account. It drops every registered database and database user first, then removes all of the account's vhosts (including the SSL ones), drops its scoped <user>_qik MySQL identity, kills anything the account is still running, and deletes the Linux user and its home directory. The panel row is deleted and foreign keys cascade the rest. If authoritative DNS is enabled, the domain's local zone is deleted too.

Termination is protected by three gates, all enforced server-side:

1. You must type the exact username into the dialog.
2. You must enter a current code from your own authenticator app.
3. If you have not enabled two-factor on your admin account, the dialog refuses and links you to vWHM → Security to set it up. There is no way around this.

A wrong or missing two-factor code is itself recorded, as account.terminate_2fa_fail.

Admin notes

A private free-text field (up to 5,000 characters) for whatever you need to remember about this client. Visible to administrators only — the account owner never sees it.

SSH / shell access

Toggles whether this account may log in over SSH. Disabling sets the login shell to nologin and hides the SSH and Terminal pages from the customer's panel. File Manager, cron jobs and Java apps keep working, because none of them need an interactive shell.

DNS and email setup

A one-click Cloudflare setup for any main or addon domain on the account. It creates the Cloudflare zone if it does not exist, then adds the full record set for a working website and mailbox: A @, A www, A mail, MX, SPF and DMARC.

Existing records are left alone, so it is safe to run again. The domain is checked against this account's own domains before anything happens.

If the zone was newly created, the result message names the two Cloudflare nameservers you must set at the domain's registrar. Nothing resolves until that is done, and that step cannot be automated from here.

Domain, DNS and HTTPS

Lists the two A records (@ and www) to add at any DNS provider, pointing at this server's detected public IP, and links to downloadable DNS instructions and a Cloudflare import file for this domain.

Below that, the current HTTPS state:

• trusted certificate — a real certificate is installed; the expiry date is shown.
• self-signed (auto) — the domain answers on HTTPS with the automatic certificate. An Enable HTTPS now button appears for accounts created before automatic HTTPS existed. For a padlock direct to the server, issue a trusted certificate from SSL / TLS.

Java, Kafka and Redis

Three independent per-account toggles, all off by default.

• Java hosting — when on, the account sees a Java Apps page in vPanel and can deploy executable .jar files, each as a sandboxed service under its own Linux user. Turning it off only hides the page; apps already deployed keep running and stay manageable from vWHM → Java Apps.
• Kafka — when on, the account gets its own SASL credentials and can create topics under its private <username>.* namespace on the shared broker. The card refuses to enable it until the broker is installed from vWHM → Kafka. Turning it off revokes the credentials; the topics remain but are unreachable until re-enabled.
• Redis — when on, a Redis card appears on the customer's vPanel dashboard with connection details for 127.0.0.1:6379. If Redis is not yet installed on the server, enabling it installs it first; if that install fails, nothing is changed. Turning it off hides it from their panel.

Databases and domains

Two read-only tables at the bottom: every registered database with its database user and creation date, and every domain on the account with its type (main, addon or sub) and document root.

If a database exists in MySQL but is missing from this list, it was created outside the panel. Adopt it from vWHM → Resources or vWHM → Unassigned DBs — see Unassigned databases.