ZoophostDocs

Server actions and reinstalls

Request restarts, power changes, rescue mode, password resets and OS reinstalls, and understand how requests are handled.

Cloud VPS3 min read

Server actions are requests handled by the Zoophost team. They are not instant API calls: the console records the request, the team performs it, and the request closes with a note.

Available actions

Open the server → Server actions.

Action What it does Data risk
Restart Graceful reboot None
Power on Starts a stopped machine None
Power off Shuts the machine down Unflushed writes can be lost
Hard reset Immediate reset, like the power button Unflushed writes can be lost
Rescue mode Boots a recovery environment with the disks attached None if used carefully
Reset root password Sets a new root password and emails it None
Reinstall OS Wipes the disk and installs the selected OS Everything on the disk is lost

Revealing or updating the password, and requesting any action, requires owner or admin in the workspace.

How a request behaves

  • The server must be active and have recorded credentials.
  • Only one open request per machine is allowed at a time. Finish or cancel the current one before queuing another.
  • A request can be cancelled only while it is Queued. Once work has started it cannot be cancelled.
  • When the team completes the request, it closes with a note visible in the console.
  • Action history keeps the 25 most recent rows.

Most requests are handled within hours. Power and restart requests are usually quick; reinstalls take longer because the OS must be installed and verified.

Reinstall the operating system

  1. Open Server actions → Reinstall OS.
  2. Pick the OS template:
    • Ubuntu 24.04 LTS
    • Ubuntu 22.04 LTS
    • Debian 12
    • AlmaLinux 9
    • Rocky Linux 9
    • Windows Server 2022
    • Custom image (describe it in the instructions)
  3. Add any instructions, such as “install the SSH key from the previous build” or “keep the second disk”.
  4. Type REINSTALL to confirm.
  5. Submit.

Take a backup first. A reinstall wipes the primary disk. If the data matters, copy it off the machine before submitting — over SSH to another host or into a Z2 bucket.

After the reinstall, the new root password is emailed and the console record is updated. Host keys change; remove the old fingerprint from ~/.ssh/known_hosts before reconnecting.

Rescue mode

Use rescue mode when the machine will not boot or SSH is broken but the data must be recovered.

  1. Request Rescue mode with a note about what you need.
  2. Connect with the rescue credentials the team provides.
  3. Mount the disks and inspect or copy data.
  4. Request a normal reboot when finished.

Rescue mode does not change the installed system unless you write to the disks yourself.

Backups

Snapshots are not included with a VPS plan. The Automatic backups add-on is Rs 149 a month: nightly snapshots kept for seven days.

There is currently no snapshot or restore control in the console. To restore a machine from a backup, open a support ticket with the server name and the point in time you need. The team performs the restore.

For your own backups that you control:

  • Copy files and databases off the machine on a schedule.
  • Keep a copy in Z2 Object Storage using rclone, restic or borg.
  • Test a restore before you need one.

Recipes: rclone and backups.

Deleting a server

Deleting a server is not a console action for customer accounts. Contact support if a machine should be cancelled; cancellation at period end is covered in Payments, renewals and cancellation.

Next

  • server actions
  • restart
  • power off
  • rescue
  • reinstall
  • os
  • backups
  • snapshots

Ready to use this

KVM machines with dedicated vCPU and full root access.

  • Root access from the first tier
  • Backups are a separate add-on
See Cloud VPS plans
Still stuck? Open a ticket from Support tickets in the console, or email [email protected]. Include the service name, the exact error and what you already tried.