What to Do If Your VPS Is Unreachable or You Are Locked Out

A VPS that suddenly won't answer is stressful, but the cause is usually one of a few things: your own network or IP, a firewall or Fail2ban rule, a changed SSH setting, an overloaded server, or an unpaid invoice. Work through the checks below in order.

Which VPS is this for? These steps are for an Unmanaged VPS, where you log in as root and look after the server yourself. On a Managed VPS we take care of the operating system and server software, and you manage your websites in StackCP instead.

Step 1: Is it the whole server, or just SSH?

• Do your websites on the VPS still load? If yes, the server is up and the problem is SSH access only (go to Step 3).
• If nothing loads, try from a different network, such as mobile data instead of your broadband. If it works there, your own IP has been blocked (Step 3).

Step 2: Check your client area

1. Log in to your FimuroHost client area and open Services.
2. Check the VPS status. If it shows Suspended, there is usually an unpaid invoice. Currently, services are suspended about 5 days after an unpaid due date. Pay it under Billing and the service is unsuspended automatically.
3. If the status is Active and a reboot option is available on the VPS page, a forced reboot fixes a server that ran out of memory or froze. Use it only when nothing else responds.

Step 3: Read the SSH error

Connect with extra detail so you can see where it fails:

ssh -v [email protected]

                        
                    

Step 4: Use the console

A console connects you to the VPS's screen directly, like plugging in a monitor and keyboard, so it works even when networking or SSH is broken.

• If your client area or VPS control panel shows a Console, VNC or Rescue option, use it. Some consoles must first be unlocked for your IP address and give you a separate console address and password to use in a VNC viewer.
• If you don't see such an option, open a support ticket and ask for console access. Include your VPS IP address and your current public IP address.

Log in at the console with root (or your sudo user) and fix the problem:

# firewall locked you out
sudo ufw disable                 # Ubuntu / Debian
sudo systemctl stop firewalld    # AlmaLinux / Rocky

# Fail2ban banned you
sudo fail2ban-client unban --all

# SSH settings broken: check, then fix the file and reload
sudo sshd -t
sudo nano /etc/ssh/sshd_config.d/00-hardening.conf
sudo systemctl restart ssh       # sshd on AlmaLinux / Rocky

# forgot a password
sudo passwd deploy

# disk full or out of memory?
df -h
free -h

                        
                    

Once you are back in over SSH, turn the firewall back on with correct rules (firewall guide).

Step 5: If the server still won't respond

open a support ticket in the Support department, or message us on WhatsApp. To help us help you quickly, include:

• The VPS IP address and the service name from your client area
• When the problem started and what changed just before (updates, firewall rules, SSH settings, new software)
• The exact error message, and the output of ssh -v
• Whether your websites on the VPS still load

Never post your root password in a ticket unless we specifically ask for it; we can usually give you console access instead.

Avoid getting locked out

• Keep one SSH session open while changing SSH or firewall settings, and test in a second window before closing it.
• Keep a spare SSH key, and store passwords in a password manager.
• Add your IP to Fail2ban's ignoreip only if it is fixed; many home connections change IP.
• Keep recent off-server backups, so the worst case is a reinstall rather than lost data.

Need help?

If something about the VPS itself is not working (it won't start, you can't reach it, or you need console access, an upgrade or a reinstall), open a support ticket from your client area or message us on WhatsApp at 01818160926. Include your VPS IP address and what you have already tried so we can help faster.