If your VPS is not booting or you cannot connect to it, this guide will help you diagnose and fix the problem.
Log in to cp.vps.ezscale.tech and check your server's status:
The VNC console lets you see your server's screen output directly, even if networking is broken. Go to your server in VirtFusion and click VNC Console. This will show you exactly where the boot process is stuck or what error messages are being displayed.
If you added a mount entry to /etc/fstab that does not exist or has the wrong UUID, Linux may hang or drop to an emergency shell during boot. Through VNC, you will see a message like "dependency failed" or "emergency mode".
Fix: In the emergency shell (via VNC), edit fstab and remove or fix the bad entry:
nano /etc/fstab
Comment out the problematic line by adding # at the start, then reboot:
reboot
If your disk is 100% full, the OS may fail to boot or services may crash. Check via VNC or rescue mode:
df -h
Fix: Remove unnecessary files to free space:
# Clear old package caches
sudo apt clean # Ubuntu/Debian
sudo dnf clean all # AlmaLinux/Rocky
# Find large files
du -sh /* 2>/dev/null | sort -rh | head -20
# Clear old logs
sudo journalctl --vacuum-size=50M
A kernel panic usually happens after a bad kernel update. You will see "Kernel panic - not syncing" on the VNC console. This typically requires an OS reinstall.
Bad network config will not prevent the VPS from booting, but you will not be able to SSH in. Use VNC to access your server and fix the network configuration.
Some OS templates offer a rescue boot option in VirtFusion. This boots a minimal Linux environment where you can mount your disk and repair files. Check your server's Power menu for rescue options.
WARNING: Reinstalling the OS will erase all data on your VPS. Only do this if you have backups or the data is not important.
Go to your server in VirtFusion → Power → Rebuild. Select your desired OS template and confirm.
/etc/fstab, double-check your work before rebooting.df -h to avoid filling your disk.