Client area and server operations
Monitor the server status from the service details and use the power, console, snapshot and reinstall screens.
Open the service details
In the client area, go to Services and open the VPS / VDS service in question. Check the service number and IP address. CPU, RAM, disk, status, sign-in details and the event log show the information for that service.
Quick actions and the web console
Start, safe shutdown, restart, force stop and hard reset are different operations. Use the options that let applications stop safely first. Force stop and reset can cause unsaved data to be lost.
The Console Connection setting of the settings profile defaults to Through WISECP: the VNC / web console is relayed to ESXi through WISECP and the customer’s browser does not need direct access to ESXi. With Directly to ESXi the browser connects to ESXi, so port 443 of ESXi must be reachable from the internet with a valid certificate. Resetting the root / Administrator password and changing guest settings require VMware Tools to be running.
Snapshots
- On the Snapshots screen, check the plan limit and the existing snapshots.
- Create a snapshot with a meaningful name; do not start another disk operation until it has finished.
- When you restore, the VM returns to the state of the selected snapshot. Changes made after the snapshot may be lost.
- Deleting a snapshot removes only the selected snapshot; check the service number and the snapshot name one last time.
A snapshot is not a substitute for an independent backup. Before growing a disk or moving the server, review the state of the snapshot / disk chain.
Reinstalling the operating system
A reinstall removes the data on the system disk and can invalidate existing snapshots. Take an independent backup first. Verify the operating system, the password and the selected service, then complete the final confirmation on screen.
Do not start a second operation by resubmitting the page before the new installation has finished. Follow the progress in the operation log; when it completes, check networking, sign-in and resources. Run trials only on a new, empty test service.