Virtual Servers — Troubleshooting

Common VDS issues and how to resolve them.

SSH connection refused

• Confirm the server is running in Virtualizor (not stopped).
• Check your local firewall and that you use the correct IP.
• Verify port 22 is open in the VPS firewall (ufw status or iptables -L).
• Use VNC console from Virtualizor if SSH is down after a bad firewall rule.

Wrong password

• Reset the root password from Virtualizor → Root/Admin Password (or equivalent).
• If using SSH keys only, ensure your public key is in /root/.ssh/authorized_keys.

High CPU or RAM usage

• SSH in and run top or htop to find the process.
• For game servers, check player count, resource leaks, and scheduled tasks.
• Upgrade the plan if you consistently hit resource limits.

Disk full

df -h
du -sh /* 2>/dev/null | sort -h

Clear logs, old backups, and temporary files. FiveM cache and txData can grow large — plan disk usage accordingly.

Network unreachable after reboot

• Confirm the VPS has an IP assigned in Virtualizor.
• Check /etc/netplan or network config was not edited incorrectly.

Service suspended

If the VDS panel shows Suspended, check Billing → Invoices for unpaid invoices. Pay the invoice to restore service.

Still stuck?

Open a ticket with your service ID, what you changed before the issue, and output from relevant commands (no passwords).