Services

Choose the software your server needs for websites, email, databases and other hosting features.

Where to find it: Open the Server menu and choose Services.

Available to: Root only.

What this page does

Use it to choose the public HTTP stack, application runtimes, database services and browser tools, deployment access, DNS service, and mail components. The Review Plan drawer shows the actions SHM intends to take before Apply starts them.

Before you start

Service changes can install packages, remove components, rebuild configuration, reload or restart daemons, and affect every hosted account. Use a maintenance window, check backups, read dependencies, and avoid Force reinstall unless the selected service is damaged or a normal apply cannot repair it.

Service groups

Versions and modules

When a runtime is enabled, choose the supported versions and optional modules required by hosted applications. Required packages are marked and cannot be treated as optional decoration. Multiple PHP versions may coexist; a domain's active version is selected later in PHP Manager.

Apply Defaults

Apply Defaults selects SHM's recommended baseline for a new server. Review the resulting plan before applying it; defaults are a starting policy, not a substitute for knowing whether this server should host mail, DNS, databases, or customer containers.

Review Plan

Review Plan summarizes selected services, installs/removals, versions, and force-reinstall state. Resolve dependency warnings first. A service can be configured as desired but still require runtime work, so follow the live progress until every item reports a final result.

How to use it

1. Refresh current service state.
2. Select the service groups and supported versions required by the hosting offer.
3. Review required dependencies and optional modules.
4. Open Review Plan and inspect every install, removal, reload, or restart.
5. Apply once and follow progress to a final state.
6. Open Status and test representative account services.

Reviewing a service plan and following progress

Choose one HTTP stack: Balanced hosting (Nginx reverse proxy with Apache), Compatibility first (Apache standalone), or Performance first (Nginx standalone). Choose the Apache process model only when Apache is part of that stack. Review the remaining service groups before applying.

Apply Defaults selects the recommended hosting setup. Review and apply changes shows the proposed work before execution. If SHM detects existing software that must be replaced, it lists the installed software and requires confirmation. Database data or DNS state that cannot be replaced safely requires manual review; a confirmation cannot bypass that condition.

An active service operation is kept on the server, so losing the browser connection does not mean the work stopped. Reopen Services to recover progress and read the final result before starting another operation. Force reinstall is a deliberate repair operation, not a routine prerequisite for saving settings. Verify the result in Services Status, including each requested service.

For automation, POST /v1/root/services/config supports background operations and partial plan updates. Preserve the returned operation identifier, poll its status, and acknowledge only a terminal result. The root API documents the complete fields and replacement-confirmation workflow.

Result and next check

SHM saves the desired service plan and reconciles the host toward it. Verify service health, website routing, PHP/Node.js/Podman operation, database access, file transfer, DNS, and mail for the stacks you enabled.