> ## Documentation Index
> Fetch the complete documentation index at: https://docs.crazynode.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting VPS Issues

> Diagnose and fix common VPS problems — connectivity, disk space, memory, and boot failures.

Run through this checklist when your VPS misbehaves. Most issues resolve without needing to open a ticket.

## Can't SSH into the VPS

1. Confirm the VPS is **running** in the control panel.
2. Ping the IP: `ping YOUR_IP`. If it fails, use the [VNC console](/vps-cloud/managing-vps).
3. Try telnet on port 22: `telnet YOUR_IP 22`.
4. Check the firewall: did you allow port 22?
5. Use the VNC console to inspect `/var/log/auth.log` and `systemctl status sshd`.

## Server is out of disk space

```bash theme={null}
df -h
du -sh /* 2>/dev/null | sort -h
```

Common culprits:

* `/var/log/*` — rotate or clear old logs
* `/var/cache/apt` — run `apt clean`
* Docker images/volumes — run `docker system prune -a`

## Out of memory / server frozen

```bash theme={null}
free -h
top -o %MEM
dmesg | grep -i "killed process"
```

If the kernel is killing processes, either add swap or [upgrade RAM](/billing/upgrades):

```bash theme={null}
fallocate -l 2G /swapfile
chmod 600 /swapfile && mkswap /swapfile && swapon /swapfile
echo '/swapfile none swap sw 0 0' >> /etc/fstab
```

## Service won't start

```bash theme={null}
systemctl status SERVICE_NAME
journalctl -u SERVICE_NAME -n 100 --no-pager
```

Read the log carefully — it almost always tells you the exact reason.

## High CPU usage

```bash theme={null}
top -o %CPU
htop
```

Identify the process, then decide whether to tune, restart, or [upgrade the plan](/billing/upgrades).

## Network issues

```bash theme={null}
ip addr             # is the interface up?
ip route            # is there a default route?
ping 8.8.8.8        # basic connectivity
ping google.com     # DNS resolution
cat /etc/resolv.conf  # DNS servers
```

## Nothing works

Boot into [rescue mode](/vps-cloud/managing-vps) or open a [support ticket](/support/tickets) with the exact error messages and what you've already tried.