Updated May 8, 2026 The dashboard’s Console button is one button with two underlying technologies behind it. The dashboard picks the right one for the OS and current state — you don’t pick. Knowing which mode you’re in matters because they have different capabilities (file transfer, copy/paste, keyboard chords, session lifetime), so this page is the dedicated explainer. For the OS-specific access flows themselves — including the local-terminal SSH and RDP options — see Connect via SSH (Linux) and Connect via RDP (Windows). This page is just about the in-browser option.Documentation Index
Fetch the complete documentation index at: https://docs.rafftechnologies.com/llms.txt
Use this file to discover all available pages before exploring further.
Two technologies, one button
| Mode | What’s happening under the hood | When the dashboard picks it |
|---|---|---|
| SSH terminal (in-browser) | A PTY session is opened via raff-agent running inside the VM, proxied to your browser as a WebSocket. You’re getting a real shell, end-to-end | Linux VM with a public IP and a healthy raff-agent. This is the default Linux Console experience |
| VNC console | A NoVNC client in your browser connects through the hypervisor to the VM’s framebuffer. No network needed inside the guest, no agent needed | Windows VM (always — there’s no SSH-terminal option for Windows). Linux VM when no public IP, agent down, SSH disabled. Anytime you need to recover from a broken OS regardless of OS |
The decision the dashboard makes
For Linux, the SSH terminal is preferred because it’s lighter, supports clipboard, and behaves like every other terminal you’re used to. VNC is the fallback for the cases where SSH-via-agent can’t work. For Windows, there’s no SSH-terminal option, so VNC is always what you get.SSH terminal — Linux primary (default)
When you click Console on a healthy Linux VM, the browser opens a fresh terminal tab pre-authenticated against the VM asroot (or your sudo user). It looks like this:

| Capability | Status |
|---|---|
| Real shell (bash / zsh / fish — whatever the VM has) | ✅ |
| Full keyboard input, including pipes / redirects / shell-quoting | ✅ |
| Copy / paste between host and VM via the browser’s clipboard | ✅ |
| Survives navigation within the same session (until the tab closes) | ✅ |
File transfer — scp / sftp / rsync directly from this terminal | ❌ Use Transfer files from your local terminal — the in-browser terminal can’t reach your local filesystem |
| Long-running attached sessions — process keeps running if the tab closes | ❌ Wrap with tmux / screen / nohup if you need it |
| Graphical apps | ❌ Use VNC mode for X11 / GUI |
VNC console — Windows always, Linux fallback, universal recovery
When the dashboard opens VNC mode, you see the VM’s actual screen — login prompt, desktop, BIOS, GRUB menu, BSOD, anything the framebuffer is rendering.
| Capability | Status |
|---|---|
| Linux text mode (getty / tty1 login) | ✅ — the default if you haven’t installed a desktop environment |
| Linux graphical (X11 / Wayland) | ✅ — if you’ve installed GNOME / KDE / Xfce |
| Windows graphical | ✅ — login screen, desktop, everything |
| Pre-OS access (BIOS, GRUB, Windows boot menu) | ✅ — VNC attaches before the OS starts |
| Survives broken networking inside the guest | ✅ — connects through the hypervisor |
Survives raff-agent being down | ✅ — VNC doesn’t use the agent |
| Special keys (Ctrl-Alt-Del, Alt-Tab, F-keys, Sysrq) | Via the toolbar’s special-keys menu — see below |
| Clipboard | Limited — paste-into-VM works in most browsers; copy-from-VM is browser-dependent |
| File transfer | ❌ Use Transfer files for SCP / SFTP / rsync once SSH is restored |
Special keys
VNC sends keystrokes byte-for-byte, but the browser intercepts several useful chords for its own use (Ctrl-T opens a tab, F11 fullscreen, Alt-Tab switches host apps). Use the toolbar’s special-keys menu to send those into the VM:| Combo you need | Where to find it |
|---|---|
| Ctrl-Alt-Del (Windows lock screen, login, task manager) | Special-keys menu → Ctrl-Alt-Delete |
| Alt-Tab (Windows app switcher) | Special-keys menu |
| F1–F12 (boot menus, Safe Mode trigger) | Direct works for most; if browser intercepts, use the menu |
| Win key / Meta | Special-keys menu |
| Print Screen / Pause | Special-keys menu |
| Sysrq + key (Linux magic SysRq) | Special-keys menu |
Session lifetime — 1 hour
Each VNC session has a fixed 1-hour TTL from the moment you click Console. There’s no idle-disconnect inside the hour and no auto-extend. When the session expires, the canvas freezes / disconnects. The VM keeps running normally — only your viewer disconnected. Close the tab and reopen Console from the VM detail page to mint a fresh 1-hour session and reconnect to the same VM with no state loss. For long debugging or recovery sessions, plan to reconnect every hour. The SSH terminal mode doesn’t have this limit — if you’re working on Linux and don’t specifically need VNC, prefer the SSH terminal for marathon sessions.Open the Console
The same Console action opens in three places — they’re equivalent:

| Path | Where |
|---|---|
| VM detail page → Console button | Top action bar, orange |
Compute (Instances list) → row’s ⋮ → Open Terminal | Per-VM Actions menu |
| VM detail → Actions tab | Same Console action, just on a tab if you’ve scrolled past the top |
When to deliberately reach for VNC over SSH
Even for a healthy Linux VM where the dashboard would pick SSH terminal by default, there are situations where you specifically want VNC:| Situation | Why VNC, not SSH terminal |
|---|---|
| You’re about to change the firewall, sshd config, or networking | If the change locks you out, VNC is unaffected. SSH terminal would die mid-edit |
| You’re rebooting the VM and want to watch it boot | VNC sees the BIOS / GRUB / login. SSH terminal disconnects on reboot |
| You’re booting into single-user mode / GRUB recovery | The boot menu only shows in VNC; SSH terminal connects post-login |
You need graphical Linux apps (xterm, browser, IDE) | SSH terminal is text-only |
You’re recovering from a broken raff-agent | SSH terminal needs the agent; VNC bypasses it |
systemctl stop raff-agent) — the next Console click will fall back to VNC. Re-enable when you’re done.
Recovery path — the universal fallback
VNC is the always-works connection method for any locked-out scenario:- Linux — SSH config broken, firewall locked you out, disk full, single-user mode → see Recover a locked-out VM § Linux
- Windows — Safe Mode, WinRE, password recovery → see Recover a locked-out VM § Windows
Common questions
How do I tell which mode opened?
How do I tell which mode opened?
login: prompt) = VNC console. The two also have different toolbars: SSH terminal has clipboard / paste controls; VNC has the special-keys menu and disconnect button.Can I copy / paste between my laptop and the VM?
Can I copy / paste between my laptop and the VM?
Can two people open the console on the same VM at the same time?
Can two people open the console on the same VM at the same time?
Why does my Windows VM only show VNC?
Why does my Windows VM only show VNC?
The VNC session expired mid-recovery. Did I lose my work?
The VNC session expired mid-recovery. Did I lose my work?
Why is the VNC console laggy?
Why is the VNC console laggy?
- Use SSH terminal for everyday Linux work — VNC is for graphical / recovery cases
- Stay in text mode for Linux work in VNC — graphical desktops repaint a lot
- Close other tabs talking to Raff — they share rate limits and bandwidth
- For Windows, pure RDP from a local client outperforms VNC for sustained graphical work — VNC is best for getting in when RDP is broken