Skip to content
BENIBIX Learn

Web Console and Rescue Mode

Level 3 · First boot and the way back in

Two ways back into a VPS when SSH fails. The web console shows the server's screen in a browser. Rescue mode fixes a server that will not boot.

Course contentsLesson 5 of 7

Level 1 · Choosing the hosting

  1. VPS, Shared and Dedicated

Level 2 · Plans and the shared machine

  1. VPS Plans and Billing
  2. Noisy Neighbors on a VPS

Level 3 · First boot and the way back in

  1. Creating a VPS with cloud-init
  2. Web Console and Rescue Mode

Level 4 · The network around the server

  1. Cloud Firewall and Floating IP
  2. Reverse DNS for a VPS

After this lesson you can

  • Log in through the web console
  • Start a server in rescue mode
  • Fix a file on a disk that will not boot

12 mincovers 2 glossary entries

Worth reading first: Creating a VPS with cloud-init

How to get back in when SSH fails

A VPS has two ways in that do not need SSH. The web console shows the server's screen in your browser, as if a screen and keyboard were plugged into it. Rescue mode starts the server from a small spare system, so you can fix its own disk. The console is for a server that runs. Rescue mode is for one that will not start.

The web console does not use the network to reach your server. The host draws the screen straight from the machine. So it still works after you lock yourself out with a UFW rule, or break the network settings.

You log in on the console with a user name and a password, like at a real screen. That is the catch. If your user only has an SSH key and no password, the console cannot let you in. Set a password for your user early, or know where the host's reset button is.

Rescue mode is for when the server will not boot at all. Maybe a settings file is broken, or the disk is full. In the panel you switch on rescue mode and restart. The host loads a small Linux over the network, and your own disk sits there untouched.

From the rescue system you find your disk with lsblk, then attach it to a folder with mount. Now your files are under /mnt. You can edit the broken file, clear space, or copy data off. Then you switch rescue mode off and restart normally.

Both tools are worth trying once on a working server. Ten calm minutes on a quiet day teach you the steps. Learning them while your site is down is much harder.

A common mistake is to delete a broken server and start again. The data on it is lost for good. Rescue mode can nearly always get your files back first, even when the system on the disk is wrecked.

console
# lsblk
NAME   SIZE TYPE
sda     80G disk
└─sda1  80G part
# mount /dev/sda1 /mnt
# nano /mnt/etc/fstab
In rescue mode, find your disk and attach it under /mnt. Then edit the file that stops it from booting.
The console shows the screen of a running server. Rescue mode starts a spare one to fix the disk.

Worked example

Lucy fills her disk

A log on Lucy's server grows until the 80 GB disk is full. After a restart, the server never comes back up, and SSH times out.

She starts rescue mode, mounts her disk under /mnt and deletes 30 GB of old logs. She switches rescue mode off, restarts, and her site is back in 12 minutes.

The words for this lesson2

Check yourself

Your server runs, but a bad UFW rule blocks SSH. Which tool gets you in?

Finished this lesson?

Marking it complete also marks its 2 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.