basforge

Search titles, text and the “If it doesn’t work” cases.

    RU

    The provider console is your fallback — test it before making changes

    The web console in the hosting panel connects to the server like a monitor and keyboard — bypassing the network, SSH and the firewall. While it works, a mistake in sshd_config or ufw takes a minute to fix. Test it before your first change, not after you’ve locked yourself out.

    What to check in advance

    • The console opens and shows a login: prompt.
    • You can log in: the user has a password. The console knows nothing about keys — passwords only. A user created with --disabled-password or lock_passwd: true (cloud-init) can’t log in there.
    • Keyboard layout: consoles often send keys as a US keyboard would, so a password with non-ASCII characters, or with @ and # in different places on your layout, won’t type correctly. Keep the console password to Latin letters and digits.
    • Pasting: many consoles don’t support it or drop characters — a long command is easier to type.

    When it saves you

    What broke What to do in the console
    ufw enabled without an SSH rule sudo ufw allow OpenSSH
    an error in sshd_config.d, sshd won’t start sudo sshd -t, fix the line, sudo systemctl restart ssh
    your own address banned by CrowdSec sudo docker exec crowdsec cscli decisions delete --ip <address>
    the server won’t boot: an error in /etc/fstab the boot emergency shell, mount -o remount,rw /, then fix the file
    lost SSH key nano ~/.ssh/authorized_keys and a new line — type it, pasting is unreliable

    If the console doesn’t help either (forgotten password), many providers offer a “reset root password” or a boot into rescue mode with the disk attached. Find where that is in the panel in advance, too.