Home Technical How to Troubleshoot and Fix VPS Connection Issues

How to Troubleshoot and Fix VPS Connection Issues

Last updated on Sep 07, 2026

Can't reach your VPS via SSH or Remote Desktop (RDP)? Follow this step-by-step guide to isolate the cause and regain access quickly.

  1. Check the Basics:

    Before diving into complex diagnostics, verify the fundamental credentials and local settings:

    • Verify IP & Ports: Double-check that you are using the correct server IP address and default port (Port 22 for SSH/Linux, Port 3389 for RDP/Windows).

    • Credentials: Ensure there are no trailing spaces when copying passwords from your emails.

    • Local Internet & VPN: Disable local active VPNs or proxies temporarily. Some corporate or public Wi-Fi networks block default SSH and RDP ports.

    • Quick Network Test: Try connecting using a mobile hotspot to rule out local ISP or router restrictions.

  2. Access via Server Console (VNC/Spice):

    • If standard SSH or RDP fails, you can try to login to your VPS by the web-based Console (VNC/Spice) from your server Dashboard:

    • Please note that you must manually type your login credentials (you cannot copy and paste them into the console). And your password will not be displayed when you type it.

    • Once logged into the console, you can run some checks:

      • Check SSH status: sudo systemctl status ssh . If the ssh service status was disabledor inactive you can restart the ssh service by the command: sudo systemctl restart ssh

      • Verify Firewall Rules: Check if a newly added firewall rule is blocking your connection:

        sudo ufw status of sudo iptables -L

      • Check Resource Usage: High CPU or memory usage can cause network timeouts. Run curl -sL yabs.sh | bash (Linux) or open Task Manager (Windows) to see if processes are maxing out system resources.

  3. Isolate Network vs. Server Status:

    Determine whether your VPS is completely down or if local network routing is preventing traffic.

    • Open your terminal or Command Prompt and run: mtr your_server_ip (Linux) pathping your_server_ip (Windows).

    • If packet drop completely: The server is likely powered off, suffering a network disruption, or blocking ICMP traffic.

    • Check Port Reachability:

      Test the specific connection port:

      • Linux: telnet your_server_ip 22

      • Windows PowerShell: Test-NetConnection Your_Server_IP -Port 3389

  4. Perform a Soft Reboot:

    If the server is unresponsive due to resource exhaustion or hung processes, initiate a Reboot from your server's control panel. Allow 3 to 5 minutes after rebooting before attempting to reconnect via SSH or RDP.


  5. Contact Support:

    If you still cannot connect via VNC or if the server remains unreachable after a reboot, open a support ticket at https://my.servers.guru/tickets . Include:

    • Your Server IP address (you can find it from your server dashboard).

    • Output of the command mtr your_server_ipaddress (Linux) or pathping your_server_ipaddress (Windows) from your local machine.

    • Output of the command curl -sL yabs.sh | bash (from your VPS if you can login by the VNC console).

    • The exact error code shown in your SSH or RDP client.