Back to articles
DevOps & Systems

Diagnosing and Resolving Common VPS Management Issues

A detailed guide to detecting, analyzing, and fixing common VPS management errors such as inaccessible access, disk full, service failures, network issues, and SSH misconfiguration....

DPTCloud Engineering5 min read
Diagnosing and Resolving Common VPS Management Issues

Image credit: LubosHouska · Pixabay Content License

Introduction

Managing a Virtual Private Server (VPS) often involves encountering technical issues that affect system performance, accessibility, and service operation. These issues may stem from incorrect configurations, exhausted system resources, or network problems. This guide provides a detailed walkthrough for identifying, analyzing, and resolving the most common VPS management errors, helping you quickly restore your system to a stable state.

Common Errors and Solutions

1. Unable to Access VPS (SSH, Web, FTP)

This is the most frequent issue when managing a VPS. Possible causes include:

  • SSH not running or blocked by firewall.
  • IP address changes or being blocked by the provider.
  • Incorrect network configuration.

Resolution:

  • Check network connectivity and VPS IP using: ping
  • Access the VPS management console to verify SSH service status.
  • Run: systemctl status ssh to check SSH status.
  • If SSH is not active, restart it with: systemctl restart ssh.
  • Check firewall rules: ufw status or iptables -L.

2. Disk Full – Insufficient Storage Space

A full disk can prevent the system from writing data, causing service failures or system instability.

Analysis:

  • Run: df -h to check disk usage.
  • Use: du -sh /* to identify large directories.
  • Free up space by deleting old logs: sudo rm -rf /var/log/*.log.
  • Reduce system log size: journalctl --vacuum-size=100M.

Prevention:

  • Set up automated monitoring with a Bash script.
  • Use crontab -e and add: 0 3 * * * /usr/bin/find /var/log -type f -name \"*.log\" -mtime +7 -delete.

3. Services Not Starting (Nginx, MySQL, Apache)

Service startup failures can result from configuration errors, port conflicts, or resource shortages.

Resolution:

  • Check service status: systemctl status (e.g., systemctl status nginx).
  • Review logs: journalctl -u -n 50.
  • Check port usage: netstat -tuln | grep .
  • Restart the service: systemctl restart .

4. Network Errors and Unstable Connectivity

These issues may be due to incorrect network settings, router problems, or provider-side issues.

Analysis:

  • Test internet connectivity: ping 8.8.8.8.
  • Trace route: traceroute .
  • Check network configuration: ip a or ifconfig.
  • Verify correct gateway and DNS settings.

5. Incorrect SSH Configuration

Wrong SSH settings can prevent access or cause connection rejections.

Resolution:

  • Edit SSH config: sudo nano /etc/ssh/sshd_config.
  • Ensure PermitRootLogin yes if root access is needed.
  • Verify Port 22 or custom port is open.
  • Restart SSH: systemctl restart ssh.

Supporting Tools and Commands

Below is a table of useful tools and commands for VPS error diagnosis:

Function Command Description
Resource Monitoring htop Monitor CPU, RAM, and disk usage.
Connectivity Test ping Test connection to an IP or domain.
Log Analysis journalctl -u nginx View Nginx service error logs.
Run Commands as Root sudo Execute commands with administrative privileges.

Preventive Solutions

  • Set up system monitoring using Uptime Kuma for early alerts.
  • Perform regular backups with Bash scripts.
  • Apply security policies such as read-only system configuration with OverlayFS.

Troubleshooting

If the issue persists after trying the above steps, consider:

  • Accessing the direct VPS console.
  • Rebooting the VPS from the control panel.
  • Contacting technical support from your service provider.

References

Practical Verification

To verify that SSH access is properly configured and responsive, execute the following steps on a local terminal:

ssh -o ConnectTimeout=10 -o StrictHostKeyChecking=no user@your-vps-ip

Replace user with your VPS username (e.g., root or a non-root user) and your-vps-ip with the actual IP address of your VPS. This command tests connectivity to the VPS over SSH, skips host key verification (for quick testing), and sets a 10-second timeout to avoid hanging.

Prerequisites: A working internet connection, SSH client installed (default on Linux/macOS; use OpenSSH on Windows), and the VPS must be running with SSH service active and accessible via the specified IP and port (default 22).

Limitations: This test does not verify authentication success or service-level functionality—only network reachability and SSH daemon responsiveness. If the command fails, check firewall rules, VPS console status, and SSH configuration. The test is non-destructive and safe for production environments.

DPTCloud Tier III Infrastructure

Recommended NVMe Cloud VPS Plans to Deploy This Setup

Enterprise RAID 10 NVMe SSDs, CMC & FPT District 9 uplinks with Anycast Anti-DDoS and 99.99% SLA.

View 22 VPS Plans
ECO · vn-02

VPS-2E

94.600 ₫ / mo

10% VAT included

  • CPU: 2 vCPU
  • RAM: 2 GB
  • SSD: 30 GB NVMe
ECO · vn-02Recommended

VPS-3E

170.500 ₫ / mo

10% VAT included

  • CPU: 2 vCPU
  • RAM: 4 GB
  • SSD: 50 GB NVMe
BASIC · vn-01Recommended

VPS-05

457.600 ₫ / mo

10% VAT included

  • CPU: 4 vCPU
  • RAM: 8 GB
  • SSD: 50 GB NVMe

Related Articles

View all
ZaloZalo SupportDiscord0384 753 478