Quick Start
Quick Start covers the post-installation path from a licensed SHM panel to a verified server that is ready for its first customer.
Where to find it: Documentation > Hosting Manager > Quick Start.
Available to: Anyone reading the public documentation. The related SHM action still follows the role stated on its page.
What this page does
This workflow begins after SHM is installed. It connects server services, security, commercial plans, account provisioning, DNS, HTTPS, mail, databases, backups, and monitoring. The order matters because later steps depend on decisions made earlier.
Before you start
Complete Installation first and confirm that SHM opens with the correct license. Then prepare the server hostname, primary IP, nameservers, customer plan, contact address, DNS delegation, and backup destination. Do not place a real customer on the server until the final handover checks pass.
Recommended setup order
| Step | Page | What to complete | Proof |
|---|---|---|---|
| 1 | Services | Choose the HTTP stack, runtimes, databases, transfer access, DNS, and mail services; review the plan before applying it. | Required services reach a final healthy state. |
| 2 | Server Settings | Confirm hostname, addresses, nameservers, timezone, and platform defaults. | Values reload correctly and match public DNS where applicable. |
| 3 | Security and isolation | Review System Hardening, Firewall, HTTP Guard, ModSecurity, account security defaults, and backup access. | Protection is enabled deliberately and legitimate test traffic still works. |
| 4 | Account Packages | Create the customer limits and the matching feature profile. | The package shows the intended quotas and tools. |
| 5 | Create Account | Provision a test account using the same plan customers will receive. | The job completes and the account opens normally. |
| 6 | DNS Manager | Confirm the zone and registrar delegation; add or correct required records. | Authoritative DNS returns the expected records. |
| 7 | AutoSSL | Issue and install HTTPS after DNS resolves correctly. | The public site presents the expected certificate. |
| 8 | Email Accounts | Create a test mailbox and check inbound, outbound, webmail, and delivery reporting. | A real round trip succeeds and the delivery report agrees. |
| 9 | MySQL Databases | Create the database resources needed by the test application. | The application connects using account-owned credentials. |
| 10 | Backup | Run a backup and prove that its restore point can be opened. | The job completes and the restore point contains the expected scope. |
Customer handover
- Sign in as the account user, not only as root viewing the account.
- Open every enabled menu item once and confirm that conditional tools match the sold plan.
- Test the website, HTTPS, mail, database-backed application, DNS, backup visibility, usage charts, and support path.
- Give the customer their own credentials and two-factor setup instructions; do not hand over a shared administrator session.
How to use it
- Complete the setup order from top to bottom.
- Stop on any failed proof instead of continuing with dependent steps.
- Use a disposable test account for the first full pass.
- Delete or retain that account according to the provider's internal QA policy only after the server is proven ready.
Result and next check
The server is ready for customer onboarding only when the service plan is healthy, the role and package model is correct, a real test account works end to end, and at least one backup has produced a usable restore point.
Theme color