Hosts
A host represents one of your servers and the configuration it should run. The Hosts area is your starting point: browse all your servers, check their live health, and open any host to configure it.
Note
Editing a host changes its intended configuration. Changes only take effect on the server once you publish them - see Publishing changes.
The Hosts list - browse and search your serversThe host workspace - configuration tabs and header actions
The Hosts list
Select Hosts in the sidebar, or open /hosts. Signing in takes you to
Health first, which is the platform's home page; the Hosts list is one step
away from it.
Each row shows the host name, a configuration summary (application types, web server, database versions), a server usage badge, live health indicators (status, memory, CPU, disk - hover for details), and a Manage button. A host whose downtime monitoring is paused carries an orange Monitoring paused badge (see Pause downtime monitoring).
Use the search box to filter by name; the Number of Items control sets the page size. To search across groups and templates too, use the global Search.
The host workspace
Click Manage on a host to open it (/hosts/{id}). The configuration is organized into tabs,
with action buttons in the top-right header.
Configuration tabs
The tabs appear in that order, with Health open when you arrive.
Note
A host that is part of a cluster is configured on the cluster page instead, which has the same tabs apart from Backups and Logs.
Header actions
-
</>Source - switch to the YAML editor (/hosts/yaml/{id}); in Source view a GUI button switches back and a Copy button copies the configuration. -
Revisions (clock icon) - open the History view (revisions, deploys, cloning and actions).
-
Pause Downtime Monitoring (bell icon) - pause all monitoring checks of the host for 1 hour to 1 day while you work on it. The bell turns orange during the pause. See Pause downtime monitoring.
-
Reboot - open a confirmation dialog to restart a Linux server outside a cluster, including cPanel and DirectAdmin hosts.
-
Save - store changes without deploying. Save & Publish - store and deploy (see Publishing changes).
Tip
Prefer the GUI editor for everyday changes and Source (YAML) for advanced or bulk edits. Both edit the same configuration. Set your default in Profile & preferences.
When a host's configuration is empty, you can pre-fill it with Copy > From host or Copy > From template (see Templates).
Rebooting a server
Rebooting interrupts every application and service on the server. Choose a maintenance period when you can accept that interruption.
- Select Reboot in the host header.
- Check the host name in Reboot server?, then select Reboot server to confirm or Cancel to close it.
- Wait for the server to return, then check its Health tab and test your applications.
Wait for any running publication to finish before rebooting. If a reboot was recently requested, check the server status before retrying. TurboStack requires two minutes between requests. If the request cannot be confirmed, check whether the server restarted before sending another request.
Rebooting does not publish pending configuration changes. Apply those separately through Publishing changes.
The built-in assistant
The purple assistant button in the lower-right corner opens the built-in TurboStack assistant. You can ask about the open host, its Health, its threats or its configuration.
Next steps
- Publishing changes - apply your configuration to the server.
- Applications and Services - configure what the host runs.