Find the controls for your VPS

Sign in to your Fasting Host client area, open Services → My Services and select your VPS. Check the service name, public IP, operating system and current status before taking an action. Available controls depend on the service, operating system and its current state.

If an active service does not show the control you need, open a support ticket. Include the service name, the action you intended and the error message. Never send your root or Administrator password, identity documents or a verification selfie in a ticket.

Start, stop or restart with care

  • Save your work and tell affected users before restarting a server.
  • When the operating system is responding, use its normal shutdown or restart procedure.
  • A forced power-off can interrupt writes and lose unsaved data. Use it only when appropriate for an unresponsive system.
  • After requesting an action, wait for the service status to update before repeating it.

Use a browser console when available

A console provides access to the server display and keyboard. It can help investigate a boot or network problem when SSH or Remote Desktop cannot connect. Open the console control shown for your VPS; it may open in another browser tab or window.

Console access still depends on a running service and the relevant platform connections. A console is not a backup or a guarantee that the guest operating system has started successfully. Keep console links and access tokens private. If the console cannot open, record the error and contact support.

For ordinary network access, use the Linux and FreeBSD SSH guide or the Windows Remote Desktop guide.

Before rebuilding or reinstalling

Reinstalling normally replaces the operating-system disk and erases the system, applications and files on that disk. Do not start a reinstall to troubleshoot a problem unless you understand its effect on your data.

  1. Export the files, databases, configuration and other information you need to a destination you control, and check that you can restore them.
  2. Confirm the exact VPS and operating system you intend to use. Image availability and minimum RAM or disk requirements vary by plan.
  3. Check the action's displayed confirmation and data-loss warning. If its effect on any attached disk is unclear, ask support before proceeding.
  4. Arrange any downtime and keep the access details needed for the new operating system private.

Do not assume a provider backup, snapshot or restore point exists. Review the backup policy. If you only need more CPU, RAM or disk space, read the resource upgrade guide; an upgrade and a reinstall are different actions.

After a verified reinstall

Check the server's status, IP address and access details in your service page. Reconnect using the appropriate SSH or RDP guide, install the software you need and restore your own data. A legitimate rebuild can change SSH host keys; verify that you are connecting to the correct server before accepting a changed key.

War diese Antwort hilfreich?

0 Benutzer fanden dies hilfreich