Synconix Hosting Manager is a control panel for managing Linux web hosting on AlmaLinux 9 / RHEL 9. It brings together websites, PHP versions, SSL, email, DNS, databases, FTP, files, cron, and server monitoring in one place.

Who is this for?

• Account users — manage your own domains, sites, mailboxes, databases, and files.
• Resellers — create and manage multiple customer accounts with delegated limits.
• Server administrators — configure global services, versions, and defaults.

What SHM does

• Web & Domains: create addon/parked domains and subdomains; manage Nginx/Apache vhosts.
• PHP Management: select per-domain PHP versions; enable extensions; isolate with PHP-FPM.
• SSL / AutoSSL: issue and renew certificates; force HTTPS; view and import certificates.
• DNS: manage zones and records; optional DNS cluster roles.
• Email: mailboxes, forwarders, filters, spam controls (Exim + Dovecot stack).
• Databases: create databases/users and assign granular permissions (MariaDB).
• FTP / SFTP & Files: FTP accounts and an in-browser file manager.
• Cron & CLI: schedule tasks; use a web terminal for safe, scoped commands.
• Monitoring: view service health, logs, and usage; restart services when permitted.

Roles & permissions

root

Full server access: global settings, defaults, service control, and all accounts.

Reseller

Manages owned accounts within assigned limits and IPs; no access to other resellers’ data.

Account

Manages own domains, email, databases, files, FTP, cron, and SSL.

Core terms

• Account: an isolated hosting space with its own domains, mail, DBs, and quotas.
• Addon domain: a separate website under the same account.
• Parked domain (alias): points to an existing site’s content.
• Subdomain: a prefix site under a domain (e.g., blog.example.com).
• Package/limits: resource ceilings (domains, mailboxes, DBs, disk, etc.).

Account isolation & runtime hardening (must-read)

• Per-account chroot: you work inside your own private filesystem. Paths, tools, temp, and sockets resolve within your space only.
• No cross-account visibility: you can access only your account’s data and settings — browsing or reading other accounts’ files is blocked.
• Dedicated PHP-FPM per user: each account gets its own master process (e.g. user-php80, user-php81) instead of sharing with others.
• Chroot-aligned PHP: PHP-FPM workers load from the same chrooted location as your account, keeping includes, sockets, and temp files contained.
• Kernel-enforced budgets: every PHP-FPM master runs in a per-account user slice with cgroups v2 limits for CPU, Memory, and Tasks (PIDs) — tunable by the administrator.
• Blast-radius reduction: a buggy plugin or runaway script is confined to its own account; other customers and services stay safe.
• Why it matters: this depth of isolation is uncommon in shared hosting panels and meaningfully raises your security baseline.

Paths & layout (for reference)

• /opt/shm/public/ — SHM web application (PHP/Nginx/PHP-FPM front).
• /opt/shm/.shm/ — SHM configuration, state, and secrets.
• /usr/local/synconix/phpXX/ — packaged PHP runtimes and extensions (per version).
• /etc/pdns/ — DNS zones (PowerDNS), when DNS is managed locally.
• /var/log/ — service logs (Nginx/Apache, mail, DB, DNS, etc.).

Browser & access

• Use a modern desktop browser with JavaScript enabled.
• Login with the credentials provided by your administrator or during setup.
• If enforced, Two-Factor Authentication (2FA) may be required at login.

Before you start

1. Sign in to SHM and open Account → Dashboard to review your package limits and IP.
2. Add your domain in Web Manager (addon/parked/subdomain as needed).
3. Point DNS (A/AAAA/MX) to this server, or create/edit the zone in DNS Manager.
4. Request SSL in SSL Manager (AutoSSL will run when DNS points correctly).
5. Create mailboxes in Email → Accounts and test IMAP/SMTP connectivity.

Quotas & limits

Your account’s ability to create domains, mailboxes, databases, and FTP users is governed by assigned package limits. The panel will show remaining capacity and prevent actions that exceed your quota.

Privacy & security

• Passwords are stored using secure hashing; follow your organization’s password policy.
• Access to system-level tools (terminal, service control) depends on your role.
• Audit logs are available to administrators; actions may be monitored.

Where to go next

• Installation — server-side setup and prerequisites.
• Quick Start — add a domain, issue SSL, create a mailbox.
• User Guide — per-page instructions (Web, PHP, SSL, DNS, Email, DB, FTP, Files, Cron, Terminal, Monitoring).
• Troubleshooting — common issues and log locations.