VPS Not Responding: Troubleshooting Guide

If your {{COMPANY_NAME}} VPS is unresponsive or you cannot connect via SSH, this guide will help you diagnose and resolve the issue step by step.

Step 1: Verify the VPS Is Running

Before troubleshooting network or software issues, confirm your VPS is actually powered on.

1. Log in to your {{COMPANY_NAME}} client area
2. Navigate to Services > My Services
3. Click on your VPS
4. Check the VPS status -- it should show Running or Active

If the VPS is stopped:

• Click Start or Power On from the control panel
• Wait 30-60 seconds for the VPS to boot
• Try connecting again

Tip: If the VPS will not start, contact {{COMPANY_NAME}} support immediately as there may be a hardware or hypervisor issue.

Step 2: Test Network Connectivity

From your local computer, test if the VPS is reachable:

# Ping the VPS
ping YOUR_VPS_IP -c 4

# Test SSH port specifically
telnet YOUR_VPS_IP 22
# or
nc -zv YOUR_VPS_IP 22

Interpreting Results

Step 3: Access via VNC Console

When SSH is unavailable, use the VNC/console access in your client area:

1. Go to your VPS management page
2. Click VNC or Console or noVNC
3. Log in with your root credentials
4. You now have direct console access regardless of network issues

Step 4: Check System Resources

Once logged in via VNC, check if the server is overloaded:

# Check if disk is full
df -h

# Check memory usage
free -h

# Check system load
uptime

# Check for runaway processes
top -bn1 | head -20

Disk Full

If a partition is at 100%:

# Find large files
find / -type f -size +100M -exec ls -lh {} ;

# Check log sizes
du -sh /var/log/*

# Clear old logs
sudo journalctl --vacuum-time=3d
sudo truncate -s 0 /var/log/syslog.1

Out of Memory (OOM)

Check if the OOM killer terminated processes:

dmesg | grep -i "oom\|out of memory" | tail -10

If processes were killed, restart critical services:

sudo systemctl restart nginx
sudo systemctl restart mysql
sudo systemctl restart php*-fpm

Step 5: Check SSH Service

# Check SSH status
sudo systemctl status sshd

# If stopped, start it
sudo systemctl start sshd

# Check SSH configuration for errors
sudo sshd -t

# Check SSH logs for errors
sudo tail -50 /var/log/auth.log

Common SSH issues:

• Configuration syntax error: Fix the error shown by sshd -t, then restart
• Port changed: Check grep Port /etc/ssh/sshd_config and connect to the correct port
• ListenAddress misconfigured: Ensure SSH listens on 0.0.0.0 or your VPS IP

Step 6: Check Firewall Rules

# UFW
sudo ufw status

# iptables
sudo iptables -L -n

# If SSH is blocked, allow it
sudo ufw allow 22/tcp
# or
sudo iptables -I INPUT -p tcp --dport 22 -j ACCEPT

If the firewall is misconfigured and blocking everything:

# Disable UFW temporarily
sudo ufw disable

# Or flush iptables
sudo iptables -F

Tip: After regaining SSH access, reconfigure your firewall properly before re-enabling it.

Step 7: Check for Fail2ban Blocks

Fail2ban may have blocked your IP address:

# Check if your IP is banned
sudo fail2ban-client status sshd

# Unban your IP
sudo fail2ban-client set sshd unbanip YOUR_LOCAL_IP

Step 8: Check System Logs

Review logs for clues about what caused the issue:

# Recent system messages
sudo dmesg | tail -50

# System log
sudo tail -100 /var/log/syslog

# Boot log
sudo journalctl -b -1    # previous boot
sudo journalctl -b 0     # current boot

# Check for kernel panics
sudo journalctl -k | tail -50

Step 9: Reboot as a Last Resort

If you have identified and resolved the root cause but the system is still unstable:

# Graceful reboot
sudo reboot

# If the system is frozen, force reboot from client area
# Use the "Force Stop" then "Start" option

Tip: Before rebooting, save any diagnostic information you have gathered. Check uptime to see how long the server has been running and whether it recently rebooted unexpectedly.

Prevention Tips

1. Set up monitoring -- use scripts or services to alert you before resources are exhausted
2. Configure log rotation -- prevent logs from filling your disk
3. Use swap space -- add swap as a safety net for memory spikes
4. Schedule regular reboots for long-running servers (monthly)
5. Keep software updated -- security patches prevent many crashes

When to Contact Support

Contact {{COMPANY_NAME}} support if:

• The VPS will not power on from the control panel
• VNC console is also unresponsive
• You suspect a hardware or network issue on the host
• The VPS keeps crashing repeatedly after reboot
• You see kernel panic messages in logs

Related Articles

• Common VPS Issues and Solutions
• Monitoring VPS Resources (CPU, RAM, Disk)
• VPS Security Hardening Checklist

Still having issues? Contact our support team at {{SUPPORT_EMAIL}} or open a ticket at {{SUPPORT_URL}}.