Booting to Rescue Mode
If it is impossible to connect to the server (when regular access to the server is lost, or you cannot perform diagnostics using OS tools), you can reboot it to Rescue. The system that works in RAM and does not use the server’s local disks will boot.
Booting to Rescue
To boot to Rescue in the Control panel:
- Go to the Operating system tab in the server card.
- Click Change boot template.
- Select Boot to Rescue in the Boot template field.
- Click Save and reboot. Please note that you need an assigned IP address to boot to Rescue.
After rebooting, the server will be available for network connection. You can manage the server via SSH or the KVM console (if available).
You can use the terminal for SSH connection in Linux and macOS. For Windows, there is no SSH client by default, so you can install any program (for example, PuTTY).
To exit Rescue Mode, restart the server – disable it, change the boot mode to Boot from 1st HDD and then turn it back on.
Learn more about Rescue mode.
Connecting to the Server via SSH in Rescue
To connect to the server via SSH, run the following command:
ssh root@<server IP>
Where <server IP> is the IP address of the server.
The system will request the password that is located on the Operating system tab of the server card in the Control panel.
When you first log in to the server, the SSH key is saved to the ~/.ssh/known_hosts file. When reconnecting, the REMOTE HOST IDENTIFICATION HAS CHANGED error may appear. To fix it, you need to delete the host information by IP address by running the following command:
ssh-keygen -f "/home/<TRex>/.ssh/known_hosts" -R "<server IP>"
Where <TRex> is the username of the account on the local computer from which the connection is made (in most cases, it is displayed in the command line):
