If SSH won't let you in, the console will; it doesn't use the network at all.
Steps
Check that the VPS shows as running in the portal at https://noc.versaweb.com. If it's stopped, start it first. You'll need a valid login for the VPS, which is the root password or a password reset from the portal.
- Open the Serial console from your VPS page in the portal (see our console article) and log in.
- Check that SSH is running. On Debian and Ubuntu the service is
ssh:systemctl status ssh, and if it isn't running,systemctl enable --now ssh. On AlmaLinux it'ssshd:systemctl status sshd, thensystemctl enable --now sshd. Debian also starts SSH throughssh.socket, sosystemctl status ssh.socketis worth a look. - Confirm which port it listens on:
ss -tlnp | grep ssh. Check your firewall. If a command says "command not found", that tool isn't installed, so skip it:
- ufw:
ufw status. Fix it withufw allow 22/tcp. - firewalld:
firewall-cmd --list-all. Fix it withfirewall-cmd --permanent --add-service=sshthenfirewall-cmd --reload.
- ufw:
- Check whether a ban tool blocked your own address (skip this if
fail2ban-clientisn't installed):fail2ban-client status sshd. To free an address, runfail2ban-client set sshd unbanip YOUR.HOME.IP. - Check the SSH settings in
/etc/ssh/sshd_configand any files in/etc/ssh/sshd_config.d/, which can override it.sshd -Tprints the settings actually in effect. If you turned off password login but your key isn't installed, setPasswordAuthentication yes, then restart SSH withsystemctl restart ssh(Debian and Ubuntu) orsystemctl restart sshd(AlmaLinux). - Test from a second terminal on your computer:
ssh -l root YOUR.IP.ADDRESS. Leave the console open until it works.
If it didn't work
- Run
journalctl -u sshd -n 50(or-u ssh) in the console and read the last lines for the reason. - If the console itself won't connect, see How do I open the Serial console or VNC Console for my Smart VPS?.
- Still stuck? Open a ticket under Technical Support with your IP address, what you changed last, and the log lines above.