Configuration
Configuration is the root workspace for server-wide defaults and policies. It is where an administrator decides how new accounts start and how shared web, security, runtime, database, mail, FTP, package, and feature settings should behave.
Where to find it: Open the Server menu and choose Configuration. Conditional items appear only when their service is installed and available.
Available to: Root only.
What this page does
Use this index to open the settings page that owns a server-wide decision. Account-specific changes still belong in the selected account, and installing or removing a service still belongs in Services.
Before you start
Configuration changes can affect future provisioning, existing generated configuration, or every account using a shared service. Read the scope on the selected page, capture the current value, and keep a recovery path before saving.
Configuration map
| Page | Use it for | Where the result appears |
|---|---|---|
| Server Settings | Host identity and general platform defaults. | Server identity and platform behavior. |
| Security | Root credentials, API access, source restrictions, and provider security policy. | Authentication and API access decisions. |
| System Hardening | Kernel, temporary-filesystem, OOM, and runtime hardening controls. | The host runtime and persistent system policy. |
| Account Defaults | Shared IP, nameservers, default PHP, and default web policy for provisioning. | New accounts; existing resources change only where the page explicitly offers an apply option. |
| Apache / NGINX | Global settings for the installed web stack. | Generated web-server configuration and runtime. |
| HTTP Guard | Global availability, profiles, scan limits, and smart-protection policy. | Per-domain HTTP Guard controls in Web Manager. |
| PHP | Installed PHP versions, pools, extensions, and server defaults. | PHP Manager and hosted PHP applications. |
| Database | MariaDB and PostgreSQL policy, recommendations, and administration tooling. | Database services and account database workflows. |
| Mail / FTP | Shared mail and Pure-FTPd behavior. | Account mailboxes, delivery, webmail, mailing lists, and FTP logins. |
| Packages / Feature Profiles | Reusable limits, reseller capacity, and account tool availability. | Provisioning and account navigation. |
Scope rules
- Defaults normally shape future resources; they do not silently rewrite existing customers unless an explicit apply-existing option is selected.
- Global runtime settings can require regeneration, reload, or restart before the service uses the new value.
- Package definitions are reusable policy. Apply the intended package to an existing account when that account must receive the changed limits.
- Feature profiles affect both visible account navigation and backend permission checks.
How to use it
- Open the configuration page that owns the exact setting.
- Read its current value, scope, validation, and apply behavior.
- Change only the required fields and save once.
- Wait for any apply operation to finish.
- Reload the page and verify the affected service or a representative account.
Result and next check
The saved policy should reload with the intended value and the affected generated or runtime state should agree with it. If a page reports a pending apply, the change is not finished merely because the form was accepted.
Theme color