Forgot your server password? Reset via the web console

Forgot the root or user password on your server and can't get in over SSH? No problem — access is restored via the web console (>_ Console) in the serverplus panel: it connects to the server directly, bypassing SSH, so it needs no password. Then we reset the password in the GRUB bootloader. Below is a step-by-step for two OS families.

Important to understand. A password reset is performed from physical/console access to the server — this is normal and intended. That is exactly why the other protections (SSH keys, firewall) matter: the console is available only to you through your account in the panel.

Step 1. Open the web console (>_ Console)

• Log in to the cloud.serverplus.uz panel.
• Open the server you need and launch the web console (>_ Console) — the server's screen opens right in the browser.
• Keep the console open: all the steps below are done in it.

Can't find the console? The button is marked with a terminal icon «>_ Console». If there is no console at all, write to serverplus support — they will do the reset on their side.

Step 2. Reboot the server and enter GRUB

You need to get into the GRUB bootloader menu and edit the boot parameters.

• Reboot the server (from the panel or with a command if you have partial access). Watch the console screen from the first seconds.
• When the GRUB menu appears (the list of kernels), press e on the entry you need to edit the boot parameters. If the menu flashes by too fast — hold Shift (BIOS) or press Esc (UEFI) during boot.

Step 3. Edit the boot parameters

Find the line starting with linux (it contains the kernel and parameters). Go to its end and append the single-user mode parameter.

Ubuntu / Debian (GRUB)

Append to the end of the linux line:

rw init=/bin/bash

If the line already has ro — replace it with rw. Then press Ctrl+X (or F10) to boot.

AlmaLinux / Rocky / CentOS (GRUB)

Append to the end of the linux line:

rd.break enforcing=0

Press Ctrl+X to boot. The system stops in the emergency shell (initramfs).

Step 4. Change the password

The steps differ slightly: on Ubuntu/Debian you land straight in a root shell, on RHEL you need to remount the disk.

Ubuntu / Debian (GRUB)

You are already in a root shell. Change the password of the needed user (or root):

# just in case, make sure the FS is mounted for writing mount -o remount,rw / # change the root password: passwd root # or a regular user's password: passwd myuser

Enter the new password twice. Then reboot the server:

exec /sbin/init

AlmaLinux / Rocky / CentOS (GRUB)

In the emergency shell, remount the system for writing, enter it and change the password:

mount -o remount,rw /sysroot chroot /sysroot # change the root password (or specify a username): passwd root

SELinux — a mandatory step on RHEL. So the system labels the changed password file correctly, create an auto-relabel marker, otherwise login will fail again after the reboot:

touch /.autorelabel # exit and reboot: exit reboot

Step 5. Check the login

After the reboot, log in with the new password — via the web console or, if access is set up, over SSH. If password login over SSH was disabled (recommended), the password is still needed for sudo and local login.

FAQ

Will data be lost in the process?

No. A password reset changes only the credentials — files, databases and settings stay in place. But before any operations on the server, taking a snapshot in the serverplus panel is good practice.

The GRUB menu does not appear / boot is too fast.

During startup, hold Shift (for BIOS) or press Esc (for UEFI). If the system boots instantly, try rebooting again and pressing the key in advance.

GRUB is password-protected and won't let me edit.

If the bootloader is locked with a password you also do not know, you cannot edit the parameters. In that case booting into rescue mode or contacting serverplus support will help.

After the reset on RHEL, login still does not work.

Almost always the reason is a skipped touch /.autorelabel (SELinux). Repeat the procedure and do not forget this step; the first boot after it will take a bit longer — the labels are being reassigned.

How do I avoid ending up here again?

Set up SSH key login (then no password is needed to log in), keep passwords in a password manager and keep snapshots. See the "Basic server protection" article.