shadowdao
33d1da92ca
Build and deploy / deploy (push) Successful in 25s
Covers the opt-in LUKS2 encryption of /docker available on new server installs. Reboot UX (web unlock at :8444, SSH fallback), threat model in plain English, what LUKS does and doesn't protect against, header backup handling, passphrase rotation outline, and the "do not enable this if you need unattended reboots" caveat. Sidebar order 7 (after Backups in the admin section). Linked from the admin overview "What's in this section" list and from the VDS comparison section of "What is containerized hosting?". No cost / pricing language by design — operational positioning is still being decided.
70 lines
4.5 KiB
Plaintext
70 lines
4.5 KiB
Plaintext
---
|
|
title: Admin overview
|
|
description: What WHP super admin unlocks — server-wide controls for services, mail, DNS, security, monitoring, and users.
|
|
sidebar:
|
|
order: 1
|
|
---
|
|
|
|
import SuperAdmin from '~/content/partials/super-admin-callout.mdx';
|
|
import Support from '~/content/partials/support-link.mdx';
|
|
|
|
<SuperAdmin />
|
|
|
|
## What super admin unlocks
|
|
|
|
WHP's super admin role exposes server-wide pages alongside the customer-facing nav. The customer pages (Sites, Domains, Email, etc.) work identically for everyone; the admin pages sit alongside them and are gated to the super admin only.
|
|
|
|
**Today, the only super admin is the `root` user on the server.** There's no UI to add another super admin — if you need additional people to have super admin, share the root credentials via your usual secret-sharing flow (or [open a ticket](https://secure.anhonesthost.com/submitticket.php) if you need a different model).
|
|
|
|
This typically applies to customers running a [Virtual Dedicated Server](https://anhonesthost.com/vds) — they get full server control as part of the plan and sign in to WHP as `root`.
|
|
|
|
### Signing in as super admin
|
|
|
|
import AdminSignIn from '~/content/partials/admin-signin.mdx';
|
|
|
|
<AdminSignIn />
|
|
|
|
## Admin-only sidebar sections
|
|
|
|
When you sign in as a super admin, these sections appear in addition to the customer-facing nav:
|
|
|
|
- **AI Monitor** — the admin dashboard, plus **Issues**, **Site Reports**, and **Ignore Rules**.
|
|
- **Security Management** — security policy across the server.
|
|
- **Coraza Rules** — Web-application firewall (WAF) rule tuning, audit, and global mode.
|
|
- **User Management** — create WHP users, set account types, manage existing users.
|
|
- **User Resources** — per-user CPU/RAM/disk allowances and current usage.
|
|
- **Delegated Users** — list of contractor / sub-account access grants.
|
|
- **Active Sessions** — every signed-in browser across the server.
|
|
- **Server Settings** — System, Services, Mail, DNS, Network & SSL, Security tabs.
|
|
- **Disk Usage** — server-wide disk consumption breakdown.
|
|
- **Announcements Management** — edit the announcements that appear on every customer's dashboard.
|
|
- **Update Management** — apply WHP platform updates.
|
|
- **Docker Management** — see and manage every container on the host.
|
|
- **Valkey Admin** — server-wide Valkey configuration.
|
|
- **Container Boot & Health** — boot-order and per-container health.
|
|
- **Site Disable Audit** — record of sites disabled / re-enabled.
|
|
- **Account Suspensions** — suspended customer accounts.
|
|
|
|
## What's in this section
|
|
|
|
- **[Server settings & services](/whp/admin/server-settings/)** — the six tabs under Server Settings: system info, restart services, mail-server config, DNS / nameservers, HAProxy + SSL, and integration API keys.
|
|
- **[Coraza WAF rules](/whp/admin/coraza-waf/)** — set the global WAF mode, tune individual rules, and audit blocked requests.
|
|
- **[AI Monitor, Issues & Ignore Rules](/whp/admin/site-monitoring/)** — the three pages that drive the Site Monitoring add-on.
|
|
- **[Users & delegated access](/whp/admin/user-management/)** — create accounts, set account types, delegate access, and handle suspensions.
|
|
- **[Backups](/whp/admin/backups/)** — configure the default backup target so customer auto-backups start running. Full-server backups are a separate, plan-dependent concern.
|
|
- **[Data-drive encryption (LUKS)](/whp/admin/data-drive-encryption/)** — optional at-rest encryption of the `/docker` data volume. Available only on new server installs; adds a manual unlock step after every reboot.
|
|
|
|
## Things to know before you change server-wide settings
|
|
|
|
- **One change can affect every site on the server.** Where customer-side pages scope changes to one site, admin pages typically scope to the whole server.
|
|
- **Service restarts are visible to live traffic.** Restart Apache or PHP-FPM during a quiet window when possible.
|
|
- **Customer backups don't cover server config.** The [customer backups](/whp/how-to/backups/) you've configured snapshot site files and databases, not server-level changes you make by hand. Server config lives in several places — not just `/etc` — so the right safety net is a **full-server backup**. On AnHonestHost-managed plans and VDS we handle that for you; running WHP elsewhere, the operator is responsible. See [Backups](/whp/admin/backups/) for the full picture.
|
|
|
|
## Related
|
|
|
|
- [What is containerized hosting?](/whp/getting-started/what-is-containerized-hosting/) — differences between container plans and full server access.
|
|
|
|
## Still stuck?
|
|
|
|
<Support />
|