Prepare the owning account
Use an active managed account with a website allowance and enabled websites feature. Read the current website capability response. A menu label for Apache, Nginx or LiteSpeed does not prove that the engine is installed or supported. Current qualification reviews Nginx with optional Apache compatibility and a supported PHP runtime.
Create a website
Open Websites → New website or the Customer Domains Manager. Choose the owning account, a primary domain, aliases/subdomains, static or PHP mode, the advertised PHP version, document root and optional advanced routing. The root is relative to the account public tree; never enter another account's path or a private server directory.
The website request includes account_id, primary_domain, aliases, subdomains, mode, apache_compatibility, php_version, document_root, php_ini, redirects and custom_errors. The backend rechecks ownership and supported capabilities. Keep the returned durable operation and verify the actual local response before changing public DNS.
Aliases, subdomains and redirects
Aliases and subdomains belong to the same managed target and account. Domain ownership conflicts cannot be fixed by creating the name in another module. A redirect records source_host, target_url, status_code and preserve_path; review the displayed source and destination so you do not create a loop or send a private path to an external site. The parser accepts the supported form and default 301 status. Custom error pages pair an allowed status_code with an account-relative path.
Modify and follow the website workspace
Reopen current detail before editing. Modification includes revision and the reviewed configuration. File, Database, PHP, Email, SSL, Backups, Logs and Applications tabs depend on permissions and actual module availability. A website database is a separate managed resource, and an SSL request is separate from ordinary HTTP provisioning.
Suspend, reactivate and terminate use the current website revision and durable operations. Preserve original operation IDs after interruption; do not erase a terminal/compensation record to retry creation. Domain changes with managed HTTPS need the installed certificate ownership/state checks.
Verify access
First inspect local service and workload health, then authoritative DNS, firewall exposure and independent public HTTP/HTTPS. A loopback response does not prove public routing. The candidate retains unresolved installed website/native recovery acceptance; use a disposable VM and keep provider recovery available. Dynamic DNS, automatic cloning/staging, dedicated cache management and a one-click website migration interface are not implemented. Apache compatibility does not make Nginx interpret .htaccess directly.