Connect to your VM

Two ways in: SSH for everyday work, and the browser-based console for everything SSH can't reach, including a VM with broken networking or no public IP at all.

SSH

Every Linux VM is provisioned with a scamp user. Grab the public IPv4 from the VM details page and connect:

Terminal 
ssh scamp@YOUR_PUBLIC_IP

If you added an SSH key in the wizard, the login is passwordless. If you generated the key through ServersCamp, download it first and fix its permissions:

Terminal 
chmod 600 ~/Downloads/your-key.pem
ssh -i ~/Downloads/your-key.pem scamp@YOUR_PUBLIC_IP

Password login works too if you set an OS password in the wizard (or kept the auto-generated one shown after creation).

If SSH does not connect

  • Security group. The VM's security group must allow inbound TCP 22. Check the Security Groups tab on the VM details page.
  • Public IP. No public IPv4 attached means nothing to SSH to from outside. Attach one on the VM details page, or use the web console below.
  • VM state. The VM must be running. The details page shows live state.

Web console (VNC)

Every VM has a browser-based VNC console: a real screen and keyboard attached to the machine, independent of the guest's network stack. If you locked yourself out with a firewall rule, broke the network config, or the VM has no public IP by design, the console still works.

  1. Open the VM in the Cloud Panel
  2. Go to the Console tab
  3. Click Open Console: it opens in a new browser tab

The console requires a running VM. It is also the way to interact with OS installers when you build a VM from a custom ISO, Windows included.

The console is a rescue path by design: it needs no SSH, no public IP and no working network inside the guest. When something network-related goes wrong, start there.

What's next?