1. Home
  2. Knowledge Base
  3. Product
  4. Compute
  5. How to troubleshoot a Linux VM which is not reachable

How to troubleshoot a Linux VM which is not reachable

Check VM Status from CloudPe Dashboard

  1. Log in to the CloudPe Dashboard.
  2. Go to Virtual Machines.
  3. Check if the VM is running.
  4. If not, try starting or rebooting it.


Access Console

  1. Use the Console option in the CloudPe panel.
  2. If console access works, the VM is likely running fine internally.
  3. If you can take the console but still unable to run any command on it or it lags your command prompt, please check the monitoring section from the CMP advance panel of your VPS
  4. Check if the CPU or RAM utilization of your VPS is normal
  5. If resource utilization is high, you can reboot your VPS and try to access it again
  6. If the console does not respond, escalate to support.

 Verify Network Configuration

  1. Ensure the VM has a Public IP if you are connecting externally.
  2. Try to ping the public IP from your local machine
  3. If you are not able to ping the IP, even if it is attached to a VPS, please contact the support team
  4. Check Security Groups
  5. To check if the required ports are listening, click here



Check Firewall Inside the VM

1. Use the console to log in and check the firewall status:

  • Ubuntu/Debian: sudo ufw status
  • AlmaLinux/CentOS: sudo firewall-cmd --list-all

To check if the software firewall is causing any issues, please click here

Check SSH Service Status

If your VM is running and the console is accessible but you are still unable to connect via SSH, the issue may be with the SSH service itself.

Use the console to run the following checks:

  1. Check if the SSH service is running: sudo systemctl status sshd If it shows inactive or failed, restart it using: sudo systemctl restart sshd
  2. Verify SSH is listening on the correct port: ss -tlnp | grep 22 If there is no output, SSH is not listening — check your SSH config file at /etc/ssh/sshd_config for any misconfigurations.

Disk/Storage Full Check A full disk can cause a VM to become unresponsive or refuse connections:

  • df -h to check disk usage
  • If / is 100%, the VM may behave erratically

Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support
This is a staging environment