Accounts

Updated Nov 18, 2026 Markdown

The list view shows username, primary domain, plan, webserver type, status, disk usage, and a kebab menu (View, Edit, Suspend, Terminate). Filters: search, status, plan, webserver, reseller. The server searches (username, e-mail, primary domain and subdomains), filters, sorts and counts, and sends one page at a time, so every account is reachable however many the server hosts; the tab counters count all accounts. The disk column is the usage measured every 15 minutes (empty until an account's first measurement); the account's own page measures it live. Every account picker in the panel (filters and create dialogs) searches the server the same way and shows the first 20 accounts by name until you type.

Create Wizard

Field Required Notes
Username yes 3–16 chars, lowercase letters and digits, starting with a letter (no underscore). Becomes the Linux user.
Primary domain yes Not checked against DNS — the account is created whatever the name resolves to. Auto SSL's Let's Encrypt order succeeds only once the name points at the server; a failed order is listed on the account page as a setup step that did not finish. A name another account already serves (as its primary domain, an addon, a parked domain or a subdomain) is refused with 409 ACCOUNT_EXISTS — on create and when an account's primary domain is changed; nothing is changed then.
Plan yes Or "Custom" to pick package limits manually.
Webserver type yes nginx, nginx_apache, openlitespeed, litespeed (last two require the matching plugin active). apache (Apache alone) is listed only on a server installed with Apache alone; on an nginx or nginx + Apache server an API request for apache gets nginx_apache (Apache behind nginx), because nginx holds the public ports and an Apache-only site would get no traffic. OpenLiteSpeed and LiteSpeed run the whole server: on a server running neither, an account cannot be put on one alone (422 VALIDATION_ERROR). Changing the web server on Edit Account moves every name of the account — primary, addons, subdomains and parked domains — each with its own PHP version, document root and redirects, and a name with a certificate keeps HTTPS (built from its certificate record, uploaded or Let's Encrypt); the web servers' configuration is tested once and both are reloaded. When the test refuses, every file is put back, the account stays on its web server, nothing else in that save is applied and the panel shows the reason (500 VHOST_CONFIG_ERROR). Asking for the web server the account already runs changes nothing.
PHP version yes One of config.php.installed_versions. Default = config.php.default_version.
Account IP optional Defaults to primary server IP. Pick a secondary IP for SNI separation.
Password yes At least 8 characters and at most 72 bytes (UTF-8; a character outside ASCII counts as more than one byte). Bcrypt-hashed, copy-on-create dialog shows it once. The same limit applies to the account password dialog.
Email optional Used for password reset and notifications.
Auto SSL yes Orders a Let's Encrypt certificate for the primary domain in the background after the account is created, with no DNS check of its own (see Primary domain); a failed order does not undo the account and is listed on the account page as a setup step that did not finish (the certificate order runs after the answer; the one step the answer itself can already name is fail2ban, and the create screen then shows a warning — see Web-scan jail). Turning it off later on the edit form takes the primary domain back to plain HTTP and deletes its certificate.
Setup mail + DNS yes Provisions Postfix virtual mailboxes, OpenDKIM key, PowerDNS zone.

The wizard runs server-side as a single transaction — failures roll the user back (no orphaned Linux user, no orphaned vhost).

Create Account stays off, with a spinner, until the form's defaults have been read from the server: the server's IP list (the IP field takes its first address), the installed PHP versions and the web server; Create Reseller Account (Resellers → Create) waits for the IP list. A press the form refuses sends nothing: each refused field shows its reason, the first one takes the focus and a notice asks you to check the highlighted fields. If the IP list cannot be read, the IP field says so and offers Retry.

Account Detail

The header carries the actions (Edit Account, Login to Client Panel, Change Password, Change IP Address, Suspend / Unsuspend, Terminate). Below it the page is divided into tabs; the open tab is part of the address (?tab=), so a reload or a shared link opens the same tab.

Apart from Overview, each tab is the matching management page of § 11 for this account alone: the same lists, sub-tabs, search, sorting, pages and actions, without the account picker or the Account column; a create or install dialog has the account filled in and locked.

OverviewUsage Trends (disk, CPU, memory), usage against the package (disk, bandwidth, CPU, memory, processes, domains, databases, email accounts, FTP accounts, disk read and write throughput), Account Information — its Home Directory row opens the File Manager tab at the account's home — and Package Limits (plus Reseller Limits for a reseller). The Domains card counts the primary domain and the addon domains, the same count the addon-domain limit checks. CPU, memory, processes and disk throughput are the live use of the account's resource slice (its Python and Node.js apps; PHP-FPM, cron jobs and shell sessions run outside it), CPU and throughput averaged since the previous reading, over one second on a first one. Usage Trends records CPU and memory every 15 minutes as a percentage of the plan's limits, from the same slice; the hourly email row of Package Limits shows the mail sent this hour (UTC) against the limit. The bandwidth figure is the account's traffic of the current month (UTC) — its sites' web bytes (a Python or Node.js app's domain included, counted once from the web server's log of that domain), the email it sends and receives with IMAP / POP3 sessions, its FTP transfers — counted every 15 minutes from the services' logs; the account and the operator are notified at 80 % and 100 % of the plan's bandwidth_mb (Bandwidth Limit Warning), and traffic.suspend_on_limit in agent.conf suspends it at 100 %. The disk and bandwidth gauges print MB below 1 GB and GB from 1 GB; a package limit of 0 shows Unlimited with no percentage.
DomainsThe Domains page: Domains (primary and addon), Subdomains, Parked Domains and Redirects with their add, edit and delete actions; a document root opens the File Manager tab there.
DNSThe DNS page: the zone of the account's first domain opens at once and the domain picker lists only this account's domains; add, edit and delete records, search, type filter, sorting, DNSSEC on or off.
SSLThe SSL page: the account's certificates — install (Let's Encrypt or a custom certificate), renew, details, delete; Secure All Domains requests certificates for this account's domains that have none.
DatabasesThe Databases page: Databases (create with a first user) and Users — passwords, access to a database, remote hosts, phpMyAdmin, delete.
EmailThe Email page's Accounts and Forwarders: mailboxes with quota or unlimited, active or inactive, password, webmail; forwarders. The server-wide Mail Queue and Sent Summary stay on the Email page.
FTPThe FTP page: every FTP account — the account's default FTP user included — create, edit, password, delete; a directory opens the File Manager tab there. The server-wide orphan clean-up stays on the FTP page.
File ManagerThe File Manager on the account's home directory; the open folder is part of the address (?path=) and the browser's Back button walks back through the folders. A folder with thousands of entries opens with its first 200 rows and draws the next ones as it is scrolled; the item count, sorting, select all and the actions on a selection cover the whole folder.
Cron JobsThe Cron page: presets, the enable switch, Run Now, edit, delete.
BackupsThe Backups page's Backups and Schedules: take, restore, download and delete archives, schedules. The server-wide Remote Storage and Settings stay on the Backups page.
IP BlocksThe account's own block list: addresses and networks refused (403) on this account's sites only — every vhost of the account carries the list, the server firewall and other accounts are not touched. Block Address takes one IPv4 / IPv6 address or a network up to /16 (IPv4) or /48 (IPv6) with an optional note; the trash icon unblocks after a confirmation. The customer manages the same list on the client panel's Firewall page.
ActivityThe Logs page's Admin Logs for this account, newest first, with the event filter, search and pages. Entries left by an earlier account that had the same username are listed too.

Once the open tab has loaded, the page reads the other tabs' lists in the background, so a tab opened afterwards shows its list at once (the File Manager its home folder) — DNS reads its zone when it is opened. The account page's tabs carry no counters; the sub-tabs inside a tab keep theirs. A tab's own sub-tab is part of the address as ?view=; another account tab starts on its first sub-tab and the File Manager on the home directory.

Suspend / Unsuspend / Terminate

  • Suspend stops mail delivery, rewrites the vhost of the primary domain and of every addon, subdomain and parked domain to a 503 page, blocks SSH, disables every FTP user of the account (the daemon refuses their next login), and reflects in the Linux account flags. A domain whose suspended vhost fails the web server's configuration test is left as it was and named in the audit entry (vhosts_left_serving); the rest are suspended.
  • While suspended the account's domains keep serving the 503 page whatever is changed on them: a PHP version, SSL, redirect, WAF or custom vhost change is saved into the configuration the suspension keeps aside and takes effect when the account is unsuspended. No domain can be added to a suspended account — an addon, subdomain or parked domain is refused with 403 ACCOUNT_SUSPENDED until the account is unsuspended.
  • Unsuspend restores the vhosts the suspension took down, with the changes made during the suspension, the credentials, the FTP users and the account's own SSH / Shell Access setting (an account created without a shell does not gain one).
  • Change Password also gives the account's default FTP user (<user>_<user>) the new password; FTP users the account added itself keep theirs. It ends the account's open client panel sessions (the customer's own and a "Login to Client Panel" session): the customer signs in again with the new password. The same applies to a change made by a billing system's API key.
  • Terminate is destructive and runs the cascade: SSL → DNS → DB → FTP → PHP-FPM pool → vhost → backups → user; the account's panel notifications and notification settings go with it, so an account created later under the same username starts with none. It runs after a plain confirmation dialog that warns the data is deleted for good; nothing has to be typed.
  • What a termination removes, and what stays. Removed with the account: its Linux user and home folder (site files, mail, its sites' access logs), its databases and database users, mailboxes and forwarders with their webmail records, FTP users, DNS zones, certificates, cron jobs, hosted apps, PHP pools, WAF rules, resource limits, backup schedules and the backup archives kept on this server, the API keys bound to the account, its traffic counters (every month) and resource history, its notification settings and the notifications addressed to it, and what the sign-in remembers about it (lock-out counters, the addresses its second factor trusted, the addresses the new-address notice has seen; for accounts terminated before this version, those addresses are removed at the agent's next start). An account created later under the same username inherits none of it. Kept, as the server's own record of what was done — none of it serves the account: your notification inbox entries about it (created, suspended, terminated…; the inbox keeps the newest 500), the API access log (each call an API key made: key, caller address, path, status; the newest 5,000 lines, trimmed to 4,000 — a billing system's key logs the billing server's address), the audit log (sign-ins with the visitor's address and every recorded action; the newest 10,000 entries, older ones in two archives of up to 50 MB each) and the agent log (100 MB × 10 files). Replies stored for repeated API requests expire after 24 hours. Copies already sent to remote backup storage stay there under that storage's own retention, and the web server's own access log follows the operating system's log rotation.

Reseller Toggle

Any account can become a reseller. Once flagged, the account gains its own scoped account tree and can be given a Reseller ACL plan (see § 5). Assigning a plan is optional: a reseller with no plan is unrestricted. Choose No ACL Plan in the account edit form to remove an assignment. Terminating a reseller terminates its sub-accounts with it (the confirmation dialog says so). Suspending a reseller suspends its active sub-accounts too, and unsuspending it brings back the ones that were suspended together with it. Each of those sub-accounts is suspended the way a direct suspension does it: sites, sign-in, cron, FTP logins, mail and hosted apps. A reseller that still owns sub-accounts cannot be turned back into a plain account — move or terminate them first.

SSH / Shell Access

The account create and edit forms carry an SSH / Shell Access switch. It sets the Linux login shell of the account's system user and, when off, also refuses the account at the SSH server itself — so no shell, no SFTP and no port forwarding. The site, cron jobs, the file manager and FTP are unaffected either way: the panel runs that work with its own shell.

New accounts are created with the switch off. Accounts that already existed keep the shell they have until an operator changes it; the form shows the account's real shell, not a stored guess.

Note that an account with shell access can reach services listening on localhost (the database server among them) from its shell, which no per-account setting can prevent. Grant it deliberately. An SSH port forward, agent forward, tunnel or X11 session from a hosting account is refused: every account is kept in the whost-accounts group (reconciled at every agent start) and the installer's sshd drop-in withdraws those features for that group only, so the operator's own sessions keep their port forwards.

Endpoints used: GET /accounts, POST /accounts, GET /accounts/{u}, PUT /accounts/{u}, DELETE /accounts/{u}, POST /accounts/{u}/suspend, POST /accounts/{u}/unsuspend, PATCH /accounts/{u}/password, GET /accounts/{u}/usage.

Still Need Help?

Our support team is here around the clock for anything you can't find above.