Inspect before changing
EPAdmin Your Server separates Builder, Stack Builder, PHP, DNS, SSL, Mail and security destinations. server:read authorizes server observations; server:manage authorizes eligible changes. Hosting, installation and security grants remain separate. Read the observation time, registered capability and current health rather than assuming a menu is supported.
Server snapshots and inventory expose CPU/RAM/load, disk and mount information, network addresses/traffic and managed service state. Account usage is separately scoped and dated. Disk/traffic counters do not establish a full historical monitoring or billable bandwidth system. CPU/RAM history, arbitrary storage-volume provisioning and connection monitoring are explicit missing features.
Service controls
Use the registered managed-service list and the supported start/stop/restart action. The UI first calls /v1/server/preview, displays validated impact and exact confirmation, then submits /v1/server/operations with preview ID and idempotency key. It does not accept an arbitrary executable or command. Shared web/PHP/mail/database service changes can affect many accounts; review the actual impact and maintenance conditions.
Hostname, network and reboot
Desired hostname/service changes must use their supported typed preview. A basic installation metadata save is not a Linux change. Keep your authenticated operator console and independently verified management route available before network or reboot work. Reboot management is distinct from unimplemented OS/package/security-update automation.
Observe processes and limits
Process inventory and reviewed termination use the process-specific identity/freshness checks, not a caller-supplied arbitrary PID alone. Account CPU/memory/I/O reports are not proof of package guarantees. Resource usage can be unavailable while the interface is healthy; preserve that state rather than substituting zero.
Verify and troubleshoot
Follow the durable operation, inspect final service/read-back state and test affected applications independently. An active PID alone does not prove startup reached its expected executable/confinement policy. Preserve operation and correlation IDs and compare unaffected services after change. Missing capabilities, conflicting ownership or unknown host files are stop conditions. Complete Tweak Settings, Server Profiles, arbitrary package management, file-permission repair and general Web Terminal are not implemented. The candidate's native hosting/reboot/recovery acceptance must still be completed on a disposable VM.