active, you have two ways to connect:
The dashboard’s Console button always opens VNC for Windows VMs (in-browser RDP is not offered). For real RDP, use a desktop client against the VM’s public IPv4.
Before you start
- The VM is
activeand has a public IPv4 (visible on the detail page) - The Administrator password — find it in the Credentials card on the detail page (use Send to Email if it isn’t visible)
- The attached security group allows inbound TCP/3389 from your IP (default Windows templates allow it; tighten to your office IP for production)
1. In-app console (VNC)
Open it the same way as for Linux VMs — Console button on the detail page, or the row’s 3-dot menu → Open Terminal. The in-app console for Windows uses VNC and gives you the full graphical desktop in the browser.
Use VNC when:
- The VM has no public IPv4
- TCP/3389 is blocked by the security group
- RDP isn’t running yet (e.g. first boot, recovery)
- You misconfigured the network or got locked out
2. Direct RDP (desktop client)
Connect from any RDP client. The connection details are the same everywhere:Windows
Pick any of:- Remote Desktop Connection (
mstsc) — built into every Windows install. PressWin + R, typemstsc, paste the public IPv4, click Connect. - Windows App — Microsoft’s modern client (replaces “Microsoft Remote Desktop” on the Microsoft Store). Adds saved-PC management and gateway support.
- Royal TS — paid, optional. Good if you manage many servers; supports tabbed sessions, credential vaults, multi-protocol (RDP/SSH/VNC).
macOS
Pick any of:- Windows App — Microsoft’s official RDP client on the Mac App Store (replaces the older “Microsoft Remote Desktop”). Free, recommended.
- Royal TSX — paid, multi-protocol with tabs and credential vault. Good for managing many servers.
- Jump Desktop — paid, App Store. Polished UX, supports Fluid Remote Desktop in addition to RDP.
Linux
Pick any of:-
Remmina — most common GTK client.
sudo apt install remmina remmina-plugin-rdpon Debian/Ubuntu. Runremmina, click +, set protocol to RDP, fill in host and credentials. -
FreeRDP — command line, robust. Most distros ship FreeRDP 2.x; some recent ones ship 3.x with new flag syntax. Pick the matching example below.
FreeRDP 2.x (older syntax —
/key:value):FreeRDP 3.x (newer syntax — same idea, slightly different flags):Useful flags either way:/size:1920x1080— set initial resolution. Use/ffor fullscreen instead+clipboard— enable clipboard sync between Linux host and Windows VM/drive:home,$HOME— share your local home directory as a drive in the VM (\\tsclient\home)/sound:sys:pulse— forward Windows audio to local PulseAudio/cert:ignore— accept the VM’s self-signed RDP certificate (always needed unless you’ve installed your own cert in Windows)/network:auto— let FreeRDP pick the best network profile (modem / broadband / LAN) based on round-trip time
- KRDC — KDE’s bundled client; same workflow as Remmina.
Troubleshooting
- Connection refused / timeout — the security group must allow inbound TCP/3389 from your IP. Use the VNC console to verify Windows itself is up.
- Authentication failed — confirm the password from the Credentials card on the VM detail page; reset it via the Password action if needed.
- Black screen after login — usually a stuck session. Send Ctrl+Alt+Del from the VNC console and choose Sign out, then reconnect.
- No public IP — use the VNC console; direct RDP needs a public IPv4 (or a Public IP).
- Certificate warning — expected; the VM uses a self-signed RDP cert. Click Connect anyway in your client.
Next steps
Reset password
Recover access if the Administrator password is lost.
Manage power
Start, stop, reboot.