This article describes using the SpinUp Cloud Servers console to work with your Cloud Server, even when normal methods, such as Secure Shell (SSH) or Remote Desktop Protocol (RDP) no longer allow you to connect to your Cloud Server.
The console enables you to further investigate issues with Cloud Servers that have become unreachable over the public or private networks due to network issues or misconfigurations.
Create or have an active SpinUp account.
Create or have an active Cloud Server.
Connecting to your Cloud Server by using the console
Log in to the SpinUp Control Panel.
Select Cloud Servers from the left side navigation menu.
Click the name of the Cloud Server for which you want to create a console session.
A new window pops up, which you might need to allow on your pop-up blocker.
After the new window opens, you see either a Linux® SSH login prompt or a Microsoft® Windows® CTRL-ALT-DEL login prompt. If you see a blank screen, press the Enter key on the keyboard to display the output.
You can now log in to your Cloud Server by using the console.
You cannot copy from your local workstation and paste into the console directly. Instead, you should type commands, passwords, and so on in their entirety.
Common console tasks
Unresponsive over network errors: If your Cloud Server’s networking is not working properly even after a reboot, the required agent service might not be running on the Cloud Server.
On Linux, the service is known as ‘nova-agent’. On Windows, it is listed as the ‘Cloud Server Agent’.
Use the console to ensure these Cloud Servers are set to start on boot up within your operating system. After you reboot the Cloud Server, networking should be properly configured. Using the console will also allow you access to troubleshoot any other standard networking problems such as issues with DNS, routes, or network interfaces that might be down.
Hung or slow boot times: It may be helpful in certain troubleshooting situations to check on a Cloud Server that is hung up or too slow to boot, but you want to observe this issue before services such as networking or SSH are fully started.
In these cases, you can open the console to observe any messages or errors that are displayed during booting.
Fixing firewall or SSH lockout issues: For those unfortunate times when you may lose remote access to your Cloud Server through human error, such as blocking your own IP address at the Cloud Server firewall, or denying access via SSH or Remote Desktop to your designated user, you may still log in locally via the console to fix these types of problems.
Please note that any configurations that affect the operating system’s local user permissions will affect console login (for example, Windows Cloud Servers acting as part of a domain will have local administrator users disabled).