Hosted edition
Lifecycle Commands
From a server's detail panel you can trigger Nginx lifecycle actions remotely, without shelling into the box.
Available commands
| Command | What it does |
|---|---|
| Test config | Runs nginx -t against the current config — checks for syntax errors before you reload |
| Reload | Graceful reload (nginx -s reload) — picks up config changes without dropping connections |
| Restart | Full restart of the Nginx process |
| Status | Forces an immediate status check, useful if the dashboard looks stale |
How it works
Clicking a command queues it for your server's agent, which polls for pending commands and executes them. Results (success/failure, and Nginx's own output for config tests) stream back to your dashboard, usually within a few seconds.
Every command is scoped strictly to your own organization's agents — commands queued by your account are never visible to, or executable by, another organization's agent, even if server or agent identifiers were somehow known.
Command history
Every command run — who triggered it, when, and its result — is kept as an audit trail. See Historical Data and Reports for how to review it (Starter plan and above).
Roles and permissions
Running commands requires the operator or admin role. Viewers can see server status and metrics but cannot trigger commands. See Users and Roles.