Docs / Troubleshooting / What to Do When Your Server Is Unreachable

What to Do When Your Server Is Unreachable

By Admin · Feb 25, 2026 · Updated Apr 23, 2026 · 34 views · 1 min read

Immediate Steps

  1. Verify from multiple locations — try a different network, use your phone data, or ask a colleague
  2. Check provider status page — there may be a known outage
  3. Try alternative access — VNC console if available (Kazepute portal has VNC access)

Network Diagnostics (From Another Machine)

# Is the server responding to ping?
ping -c 4 your-server-ip

# Trace the network path
traceroute your-server-ip
mtr your-server-ip

# Check if specific ports are open
nc -zv your-server-ip 22
nc -zv your-server-ip 80

Common Causes

  • Firewall lockout — accidentally blocked your own IP or SSH port
  • Disk full — services crash when they cannot write logs
  • OOM kill — SSH daemon killed due to memory exhaustion
  • Failed update — kernel update requiring reboot, or broken network config
  • DDoS attack — bandwidth saturated

Recovery via VNC Console

If SSH is unreachable but the server is running, use the VNC console from your hosting control panel:

  1. Log into the Kazepute portal
  2. Navigate to your Breeze
  3. Click VNC Console
  4. Log in and diagnose the issue

Prevention

  • Always test firewall rules before disconnecting
  • Set up monitoring and alerts
  • Keep a backup SSH key and access method

Was this article helpful?