Skip to content
hostup.se

Can't reach your VPS? Troubleshoot the connection

Checked against the client area 6 November 2026

If your VPS does not answer on SSH, Remote Desktop or the web, the client area can test the connection for you. The Connection troubleshooter tries the ports for SSH, the web and Remote Desktop. For each port you see whether the server responds. The row for the port you use shows where the problem most likely is. If the server does not start at all, the console shows what is happening. From there you repair it with a rescue system or a backup.

Open your servers in the client area

  1. Go to VPS and click the server. If it is stopped, click Start.

  2. Click the Connection troubleshooter link on the Overview tab.

    The server overview with VPS in the menu, the Overview tab and the Connection troubleshooter link framed
  3. Click Run check. The check takes a few seconds.

    The connection troubleshooter with a result per port and the Run check button framed

The check tries the same four ports on every server: 22 (SSH), 80 and 443 (web) and 3389 (Remote Desktop). Look at the port you are trying to connect to. A port you don’t use usually does not answer. That is not a fault.

  • Responds: something on the server accepts connections on the port.
  • Refused: the server is up. Nothing accepts connections on the port. The service is stopped or a firewall inside the server refuses it.
  • No response: nothing answered. The server is off, has not started, or a firewall stops the traffic.

The box in the result says what the likely cause is and what to do next. If your port responds but not all of them do, it says The server is online, but some services did not respond. It then asks you to open the console and check the services that did not respond. You only need to do that for services you use. If any port does not respond, you also see the links Open console and Open firewall tab.

  • No response on your port: click Open firewall tab or open the Firewall tab. If it says Firewall Inactive, the firewall is off and stops nothing. If it says Firewall Active, traffic to ports without a rule is stopped. Add a rule for the port. See Firewall for your VPS.
  • Refused, or no response with the firewall off: open the console and check the service and the firewall inside the server. See The console (VNC). You can also run commands from the client area with Remote Commands.
  • Your port responds but the login is rejected: if you log in over SSH with a password, SSH password login must be turned on. The switch is on the Overview tab. See Turn on password login for SSH. You create a new password under Settings › Root Password › Create New Password. On a Windows server it says Administrator Password instead of Root Password. See Reset the password for your VPS.
  • Your port responds but the connection times out: the check reaches the server from our side. That does not show it can be reached from your network. Test the port from many places around the world: open ping.pe/<server IP address>:<your port> in your browser, for example :22 for SSH. If the server answers from most places but not from your network, open a support ticket. Include the public IP address you connect from (not the server’s), the port, the error message, and the time with your time zone. We can then trace the connection.

If the server does not answer at all, the console shows what happens when it starts.

  1. Click Console. The console opens in a new tab.

  2. Go back to the client area tab and click Restart. The Restart server dialog opens.

    If the button says Start instead, the server is stopped. Click it and go to step 5.

  3. If the server has hung, tick The VM is unresponsive – force stop immediately. That cuts the power straight away.

    The Restart server dialog with the force stop option and the Restart button framed
  4. Click Restart.

  5. Follow the boot in the console and read the error message there.

You then have three options, from the one that keeps the most to the one that erases everything:

  • Repair the disk: click Quick Mount next to netboot.xyz on the ISO tab, then Boot from ISO and Restart. In the console, choose Utilities and then System Rescue CD. From there you can reach the server’s disk and repair the file system. When you are done, click Unmount and restart the server. See Boot your VPS from your own ISO file or netboot.xyz.
  • Restore a backup: if you have a backup from when the server worked, restore it. Everything changed after it is overwritten. See Restore a backup of your VPS.
  • Reinstall: everything on the server is erased and you get a clean server. See Reinstall your VPS with a new operating system.
  • If the page says Bandwidth limit reached, the bandwidth has run out. You can’t open the console or start the server until you have added bandwidth or the next period has started. See Bandwidth on your VPS.
  • While another operation is running on the server, such as a backup, the console and the power buttons are locked until it has finished.