Skip to main content

How to Connect to Instances with the Instance Console

The browser console displays the Instance's virtual screen and accepts keyboard input through noVNC. It is useful for viewing startup messages or investigating a guest that cannot be reached over SSH.

Opening the console does not sign you into the guest operating system. In the check on 30 October 2026, the viewer connected and displayed an Ubuntu 24.04.5 LTS login: prompt. An OS login through that console was not performed.

Access the Instance Console​

  1. Sign in to the FibaCloud control panel.
  2. Open Instances and select the Instance you want to inspect.
  3. Open Console from its management page. If the browser blocks the new console tab or window, allow it for the control-panel site and try again.
  4. Wait for the noVNC viewer to connect. During boot, allow time for the guest to reach its login screen.

The noVNC console showing an Ubuntu login prompt; the Instance hostname is redacted

The image above is a real console capture with the Instance hostname removed. It shows a connected viewer and a guest login prompt, not an authenticated shell.

Sign in to the operating system​

Click inside the console before typing. At login:, use a valid account for the installed operating system, followed by that account's password if requested. Password characters normally do not appear while you type.

The FibaCloud account password is not the guest's password. An SSH key selected during creation authorizes SSH access; it does not automatically provide passwordless access at an Ubuntu console login prompt. A guest configured for SSH keys may not have an OS password available for console login. Use your existing SSH access or contact support for an authorized recovery path if you cannot sign in.

If the console does not respond​

  • Check the Instance's power state. A stopped Instance must be started before its OS can boot.
  • Give startup time to finish. A visible boot or login screen helps distinguish viewer connectivity from an SSH-service issue.
  • If the viewer disconnects, reopen Console from the authenticated management page rather than reusing an old console URL.
  • Check that keyboard focus is inside the viewer. Use the noVNC controls when the browser intercepts a key combination.

Closing the console tab ends the browser connection; it does not cancel the Instance or end its billing. Review billing for ongoing costs. For a restore workflow and the Startup step after a stopped restore, see snapshots.