Console and rescue

Use the browser console if you cannot connect to the server over SSH. Use Rescue if the operating system will not boot.

SSH is the normal way into a Gozunga Cloud server. It needs a security group that allows port 22, the right key, and the right username. When that path is broken, or you need to see boot messages, open Console on the server page. A terminal opens in the browser. It talks to the instance through the hypervisor, not through the public IP. It is not an SSH session, and it does not bypass the guest password or key.

When you need the console

• The server is Active but SSH times out. Often the security group was not attached. See Using Security Groups.
• You need to watch the guest boot, or send Ctrl+Alt+Del.
• You are on a machine with no SSH client.

On the server page, the header is Console, Reboot, and Shut down. Click Console. You get the guest login prompt. On Ubuntu it looks like demo-ubuntu login:. Log in as the default user for that image. Ubuntu is ubuntu. See Default Usernames for Cloud Instances.

The console toolbar includes Send CtrlAltDel. If you cannot log in here either, the guest credentials are wrong. To connect from your laptop once the network path works, see SSH Key Management.

Rescue

Rescue is for a disk that will not boot far enough to show that login prompt: a broken fstab, a failed kernel, a full root filesystem. It boots a recovery environment and sets the server status to RESCUE. You then fix the original disk from that environment.

On the server page, open Server Actions and choose Rescue.

Under Select Image, choose Operating Systems, My Images, or Volumes. For a typical Linux rescue, pick a current guest image such as ubuntu-26.04. Do not choose deploy-initrd or deploy-vmlinuz. Those are deploy artifacts, not an operating system.

When you are finished, return the server to normal operation from Server Actions. Snapshot first if you might need the disk back. See Snapshots and backups and Creating and Managing Virtual Machines.