Skip to main content

​
Overview

Xloud Compute provides browser-based and protocol-level console access to instances for out-of-band management and debugging. Console access is available regardless of network reachability — making it an essential tool for diagnosing boot failures, network misconfigurations, and OS-level issues.

​
Console Types

ProtocolProxy PortBest For
VNC6080General-purpose graphical console; available in all browsers
SPICE6082High-performance graphical console; supports audio, USB redirect, and clipboard sharing
Serial6083Text console for headless instances or boot-time debugging
RDP—Windows instances; requires RDP agent installation inside the guest
VNC and SPICE console traffic passes through the console proxy service on ports 6080 and 6082 respectively. Serial console requires port 6083. Ensure firewall rules permit inbound connections to these ports from administrator workstations and any jump hosts.

​
Open a Console

Navigate to the instance

Log in to the Xloud Dashboard (https://connect.<your-domain>) and navigate to Project → Compute → Instances. Click the instance name to open the detail view.

Open the Console tab

Select the Console tab. The VNC console loads inline in the browser window.
Click Click here to show only the console to enter full-screen mode. Press Ctrl+Alt+F2 within the console to switch to a virtual terminal on Linux guests. Use Ctrl+Alt+Delete to send a secure attention sequence to Windows guests.

Interact with the instance

Type directly in the console window to interact with the instance. Mouse input is supported for graphical environments.
Console sessions are proxied through the VNC proxy service. If the console shows a black screen, the instance may still be booting. Wait 30–60 seconds and refresh the page.

​
Firewall Port Requirements

Ensure the following ports are open between administrator workstations and the controller node before using remote console access.
ServicePortProtocolDirection
VNC Proxy6080TCPInbound to controller
SPICE Proxy6082TCPInbound to controller
Serial Proxy6083TCPInbound to controller
These ports must be accessible from the browser performing the console session — not just from the administrative CLI host. If your environment routes through a jump host or firewall, ensure the end user’s browser can reach these ports directly on the controller node.

​
Verify Console Proxy Services

Administrator Access Required — This operation requires the admin role. Contact your Xloud administrator if you do not have sufficient permissions.
Verify the console proxy service is running:
Check console proxy service status
openstack compute service list | grep consoleauth
List all compute services and their status
openstack compute service list
The console proxy service shows State: up. If it shows down, restart the service through XDeploy under Compute → Services → Console Proxy.

​
Next Steps

Security Hardening

Restrict console access using network security policies.

Troubleshooting

Resolve console connection refused errors and token expiry issues.

Admin Guide

Return to the Compute Administration Guide index.