Mei 23, 2026Gidse

Bediener reageer nie: probleemoplossing

Ping, poorte, dienste, CPU/RAM en loglêers wanneer VPS onbereikbaar is.

As jou VPS nie reageer nie — werf af, SSH-timeout, ping misluk — gebruik hierdie kontrolelys op Hiddence.

Stap 1: Netwerkbereikbaarheid

Vanaf jou rekenaar, toets die IP:

bash

ping YOUR_VPS_IP

# If ping fails: check VPS status in client area,
# possible network maintenance, or IP change after reinstall

Stap 2: Oop poorte

SSH (22), HTTP (80), HTTPS (443) kan geblokkeer wees:

bash

# From your PC (if nmap installed):
nmap -p 22,80,443 YOUR_VPS_IP

# On server (via console/KVM if SSH works):
sudo ufw status
sudo ss -tlnp | grep -E ':22|:80|:443'

Stap 3: Diensstatus

Bediener kan loop maar Nginx of SSH gestop wees:

bash

sudo systemctl status ssh
sudo systemctl status nginx
sudo systemctl status mysql

# Restart if failed:
sudo systemctl restart nginx

Stap 4: CPU, RAM en skyf

Geheuetekort of volle skyf veroorsaak dikwels vries:

bash

top -bn1 | head -20
free -h
df -h

# Kill runaway process if needed:
kill -9 PID

Stap 5: Loglêers

Loglêers wys dikwels OOM en ander foute:

bash

sudo journalctl -xe --no-pager | tail -50
sudo tail -100 /var/log/nginx/error.log
sudo tail -100 /var/log/syslog
dmesg | tail -30

Voorkoming

Aktiveer swap op klein VPS
Monitering (Uptime Kuma, Netdata)
Outomatiese rugsteun
Fail2ban met jou IP op witlys
By netwerk/toerusting — ondersteuning met VPS-ID